1. Invite the bot
The invite runs through Discord's own authorization dialog. There you select the server and confirm the permissions the bot requests. Important: you need the Manage Server permission on that server, otherwise Discord will not even offer the server for selection.
2. Drag the bot's role to the top
This is the point at which most setups fail, and it has nothing to do with us, but with Discord's permission system: a bot can only assign or remove roles that sit below its own role. If the bot's role is at the very bottom, it cannot do anything at all.
Open Server Settings → Roles and drag the bot's role up far enough that it sits above every role it is supposed to assign later: level rewards, verification role, mute role, team roles for tickets. It does not have to be above your administrators' roles.
3. Set the language
In the dashboard under Personalized Bot → Bot Language you set which language the bot speaks. This applies to everything members get to see: welcome messages, level-ups, log entries, moderation notices, tickets, giveaways.
You can choose German, English, French, Spanish, Italian, Portuguese, Dutch, Polish, Turkish and Russian. The setting takes effect immediately, you do not have to restart anything and you do not have to translate any texts yourself.
The language of the dashboard is independent of this and can be changed via the globe at the top right. So you can configure in German while the bot speaks English on your server.
4. The first three building blocks
We recommend starting with these three. They mesh together and deliver a visible benefit quickly.
Logs first
That sounds boring, but it is the most important building block, as long as nothing is logged, you are flying blind on every incident. Create a channel that only your team can see and enter it under Logs. From then on it is traceable who did what.
Then the welcome message
New members notice immediately whether a server is looked after. Under Welcome & Goodbye you choose the channel, write the text and decide whether an image card or a plain embed appears. Placeholders such as {user} and {server} are filled in by the bot.
Auto-Moderation last
Start with a few rules, anti-spam and the scam pattern filter are enough for the beginning. You can add everything else once you see what actually happens on your server. Details under Auto-Moderation.
5. Set exceptions before they become a nuisance
Every automatic rule needs exceptions, otherwise it will eventually delete something legitimate. Two settings pay off right away:
- Exempt channels: advertising or introduction channels in which links are meant to be allowed.
- Exempt roles: your team. Otherwise the bot warns your own moderators when they pass on an invite link.
Members with Administrator or Manage Server permissions are always ignored by Auto-Moderation anyway, regardless of these lists.
6. Check that it really works
A setting that has been saved is not yet a setting that works. Three quick counter-checks:
- Welcome: Leave the server with a second account and rejoin. If no message arrives, the bot is usually missing the permission to write in the chosen channel.
- Log: Delete one of your own test messages. If nothing shows up in the log channel, either the event is not enabled or the channel is set incorrectly.
- Auto-Moderation: Write a message in caps from an account without special permissions. If nothing happens, check whether your test account is accidentally listed in the exempt roles.
What you can do afterwards
From here on it depends on what your server needs. A gaming server benefits from temporary voice channels and levels; a support or sales server rather from the ticket system. If your server is advertised publicly, verification is the next sensible step against automated accounts.