Blacklists

You can blacklist users from creating tickets and reports and do some other things with the blacklists. Learn how to do this here!

Remember that entities are used to describe users and roles for the sake of simplicity.

Users can be added to one or both blacklists are are represented by a blacklist entry.

The blacklist entry states in which guild the user is blacklisted and for which module.

The module can be tickets, reports or both.

Add entities to a blacklist

Use the /blacklist add command.

You can provide the ID of

• the user directly or

• the ticket or report whose user you want to blacklist

The report or ticket ID is usually used when it's easier to copy that directly or when an anonymous ticket was opened.

You also have to select to which blacklist you want to add them.

-- Bild of command in use --

Conditional Adding

Example: If the user is already blacklisted for module A and a moderator wants to add the user to module B then the user will be blacklisted for all/both modules.

An error will only be thrown if the user already blacklisted for this module - not if a user is already blacklisted for another module.

Remove entities from a blacklist

A role is automatically removed when it was not found while executing /blacklist check or the debug option Check role integrity was selected,

Use the /blacklist remove command and either select who you want to remove or provide the ID of the entity you want to be removed.

If a blacklist entry was found for only one module, the user will be removed. If the user is blacklisted for both modules, you will be asked which module the blacklist entry should be removed from: Tickets, Reports or Both.

-- Bild of user being removed from one --

-- Bild of asking which module to remove user from --

Keep reading to learn about the other option to remove users from a blacklist.

Conditional Removing

Example: If the user is blacklisted for both modules, the moderator will be asked, from which module the entry should be removed.

The entry can be

• ,

• , or

• deleted for all/both modules.

Viewing blacklisted entities

To view a whole set of currently blacklisted users, use the /blacklist view command.

Because the amount of users can be very large, pages are established here. If you don not provide any information about the page, 1 will be used which displays the newest 25 users.

Each page displays up to 25 users.

It's displayed in the following format:

1.   

Example:

/blacklist view module:Tickets

1. @user1 [Link]
2. @role1 (All)
3. @role2
4. @user2 [Link] (All)

The outcome might look like this:

-- Bild of /blacklist view module:Tickets --

The following components attached here:

-- Bild of components --

With the select menu you can select up to 25 users from the page that is currently selected that should removed from the blacklist by selecting the user's respective number on that page.

If a user or a role is blacklisted for all modules and is selected to be removed, the entry will be removed completely and not just from that module.

Why users are numbered and not always mentioned?

We don't store usernames because it's not very reliable. So we can't display them there.

Unfortunately, this brings another problem to our attention. They are in fact mentioned. however, sometimes not all users are cached in the and appear as <@1234567890987654321>. There is nothing we can do about this, but we can find a workaround. The workaround is to add a hyperlink to the user's profile (example). This will only work while the user is still a member of the server. If the user is no longer a member of the server, the link will only work if you share another server with the user. Otherwise it won't work.

And that brings us to another problem: We can't use a user select menu here because

1. it is not possible to limit the number of available users

2. it is not possible to display users who are no longer on the server.

That's why the select menu to remove multiple users is like it is - a normal select menu.

The other 5 buttons are for pagination.

Button	Action
⏮️	First page (1) (newest entries of the module)
⬅️	Previous Page (-1)
🔢	Opens a modal to manually enter a page number (min & max are displayed there)
➡️	Next page (+1)
⏭️	Last page (oldest entries of the module)

Check if an entity is present in a blacklist

You can run the command /blacklist check with providing a or a raw ID of the entity.

It's only recommended to use the raw ID when you can't select the user because they left the server.

Clear blacklist

To get rid of an entire blacklist, an administrator has to use the /blacklist clear command. This only works for one blacklist at a time.

---

Configuration

You can use the /config blacklist command to configure, who can use which subcommand of blacklist.

You can whitelist roles, users and channels.

By default, the command is only usable with the Manage Server permission.

If you leave any list blank, it works as "All are allowed".

If you leave everything empty, it will check the Manage Server permission.