Getting started
Invite Who, understand the dashboard and get the server ready to go in a sensible order.
Invite Who to your server
Setup, Discord releases and the first dashboard call.
Before inviting
You need permission on the Discord server to add applications or manage the server. Who only requires the Discord rights that match the activated modules.
- 1
Open who-bot.de and select “Connect with Discord”.
- 2
Log in to Discord and select the desired server.
- 3
Check the bot rights displayed and confirm the invitation.
- 4
After that, open the Who dashboard and select the same server.
If the server does not appear
The server selection shows servers that your Discord account is allowed to manage, as well as servers where Who is installed and you have been granted dashboard role approval. A share only works for the modules that have been assigned to your team.
- Make sure you are logged in with the Discord account that owns the role.
- Ask the server owner to release your role under Permissions and select at least one module.
- Make sure Who is installed and accessible on the server.
- Then reload the server selection.
Understanding the dashboard
Change servers, find modules and save changes securely.
Construction
The server change is at the top of the sidebar. The modules are grouped by areas such as protection, server management, community and tools. Overview shows the current overview; Settings contains basic server-wide options.
- A module opens its own configuration page.
- A plus or minus sign indicates the activation status of the module.
- Individual settings can also have their own activation switches.
Apply changes
- 1
First choose the right server.
- 2
Only change the fields you want.
- 3
Use the save button on the page.
- 4
Check the feedback in the dashboard and test the function in a suitable channel.
Recommended initial setup
Start with a low-risk plan and release features gradually.
Proceed in this order
- 1
Create a private bot log channel and only share it with the team.
- 2
Set up server language and time zone.
- 3
Configure greeting and roles before enabling automatic protection actions.
- 4
First start protection modules with appropriate exceptions and a team log channel.
- 5
Test each change with a test account or in a private test channel.
After the test
Check whether mentions, roles and target channels are correct. Leave moderation actions at a low impact initially until the rule works reliably in real everyday server life.
Ticket limits and access rights
Limit open tickets and balance visibility with Discord channel rights.
Process and limits
You can manage up to 20 ticket panels. A panel technically supports up to 25 categories; depending on the tariff, the available limit may be lower. Up to five questions can be asked per panel or category. A limit of 1 to 10 open tickets can be set for each user. Additionally, there is a cooldown between new tickets.
- Set the limit so that a single user does not open many empty tickets.
- Use short questions with understandable examples.
- Set target category and support roles where appropriate; a category can use its own values.
Who can see a ticket?
The visibility arises from the channel permissions of the created ticket channel. Verify that ticket creators and relevant support roles have access and regular members do not have access. The Discord role of Who must be above roles that the bot should set in permission overrides.
