Frequently asked questions

Either, it makes no difference. The site and the commands write to the same database. A change made from the dashboard is picked up by the bot immediately, with no restart. It works the other way round too: a setting applied through a command shows up on the site straight away.

Only members holding the “Manage Server” permission (or Administrator), and only on servers where the bot is present. That list comes from Discord, queried with YOUR account: it is never inferred from what your browser claims, and therefore cannot be worked around. Getting in does not hand over every right either: posting in a channel, handing out a role or granting a staff level are each re-checked against your own Discord permissions. The bot never does on your behalf what you are not allowed to do.

No. You add the bot to your server, you open the dashboard, and you switch on what you need. Nothing to install, nothing to maintain on your side.

Certainly not. Every module is independent and off by default: switch on what serves you, leave the rest aside. Nothing runs in the background for a disabled module.

Message content is never stored. When logging is active, the bot posts an embed in the channel you designated: that is all that happens, nothing is kept in the database.

Your settings (which modules are active, towards which channels, with which roles), the history of sanctions issued through the bot, and XP progression if the Levels module is enabled. Nothing else.

Your settings are kept for a grace period: if you re-invite the bot before it expires, you find everything as it was. After that, the server's data is purged automatically.

Those its modules need: manage roles and channels, kick and ban, send messages and embeds, connect to voice. A permission you withhold does not stop the bot from starting: only the functions concerned stop responding.

Your Discord profile and the list of your servers, nothing more. You never type a password on the site: authentication goes entirely through Discord.

Every sanction gets a unique public code. From the dashboard or with the history command, you search by code, by member or by reason, and you can attach internal notes to a case.

Yes, when they expire. On the way, the bot checks that the ban has not been re-applied in the meantime by a moderator: if it has, it does not lift it.

You set a join threshold and the time window it is measured over. Beyond that, the bot triggers the action you chose: alert, quarantine or kick. You can also target only recently created accounts.

You set the time allowed, the number of attempts and what happens on failure. Until verification passes, the member stays in the quarantine role you designated, so you always keep the option of clearing someone by hand.

The Backups module photographs the server's structure (roles, channels, permissions) and hands you a private code. That code restores the structure. It contains no messages: a backup is not a conversation history.

Up to 25, the limit of a Discord dropdown. Each has its own emoji, colour, greeting message and opening form. On closing, an HTML transcript is archived in the channel you chose.

No. Music is a separate module, served by a dedicated audio infrastructure. If it is unavailable the bot starts normally and only the music commands answer “service unavailable”: everything else works. That infrastructure only plays back what it is asked for. It does not listen in on voice channels and records nothing.

Yes. Three staff levels are tied to roles on your server, and each moderation command requires a minimum level. You can adjust it command by command, without touching Discord permissions.

From the dashboard's “Language” screen, or with the dedicated command. Thirteen languages are available and the translation goes down to command names, their descriptions, menus, embeds and error messages. The change applies within the second.

Yes, member by member or for the whole server, from the Levels screen. You can also adjust someone's XP by hand rather than wiping everything.