Security and anti-raid

In the left menu, Configuration group, click Security. On the server home, the red "Under attack? Turn on raid mode" callout and its Open button also lead here.

1. The counters: Emergency (raid mode Enabled or Disabled) and Whitelist (number of entries, owner included).
2. Whitelist an app: adds a bot to the whitelist (see below).
3. The Raid mode block and its red switch.
4. The Whitelist: the add box, then the list of entries.

Raid mode is the emergency switch: while it's on, every new member gets a direct message and is then kicked. Members already on the server are not affected. It works even when the anti-raid is off, and the whitelist doesn't apply: nobody is exempt during that time.

It takes effect immediately, without going through the save bar.

Turn raid mode on

1. Click the switch in the Raid mode block. The Enable raid mode dialog opens.
2. Set the options below.
3. Click Enable. The message "Raid mode enabled." appears and the block turns red.

The last two options are Discord safety actions, only available on a Community server. On any other server, the dialog shows "This server does not have Community enabled — Discord safety actions are unavailable." and the switches are greyed out.

1. Duration and the computed end time.
2. The safety actions (Community server).
3. Enable.

While raid mode is on

• The Raid mode block is red and shows "Ends at: …" with "Emergency active. New members are kicked until the scheduled end or a manual disable."
• The server home shows the Raid mode active banner ("New joiners are kicked automatically until …") with an Open Security button.
• On Discord, the activation is posted in the Anti-Raid & Security Logs channel (with the emergency mentions) and each kick in Joins & Leaves Logs.

The direct message each new joiner receives:

Turn raid mode off

Click the switch again: the "Disable raid mode?" dialog reminds you that "Automatic kicks stop and Discord safety actions are cleared.". Click Disable ("Raid mode disabled.").

When the chosen duration is over, raid mode stops on its own, without any message on Discord; reload the page to see the current state.

From Discord, the /raid-mode command does the same thing with a fixed 24-hour duration (see Server management).

The whitelist says who is exempt from which anti-raid protections. Each entry (a member, a role or an app) has one or more scopes.

Add a member or a role

1. In the add box, choose User or Role.
2. Pick the member (search among the first 100 members, or paste a Discord ID) or the role.
3. Choose the covered protections in the scope picker (Global by default).
4. Click Add: "Added to draft — save at the bottom to apply.".
5. Click Save changes in the bar at the bottom of the screen ("Whitelist saved.").

Scopes

Neither raid mode nor the captcha take the whitelist into account.

1. An entry's Edit button opens the Covered protections picker.
2. Tick or untick scopes; the summary shows Global, a single scope or "N protections".

The list

• Roles come first (colour dot, Role badge), then members.
• The owner is always shown at the top of the members, with the Owner badge and the Global scope: they can't be edited or removed here.
• Bots carry the APP badge.
• For each entry: its scopes, Edit (scopes) and the cross to remove it from the draft.
• A member sanctioned with /timeout, /kick or /ban (or from the website) is automatically removed from the whitelist.

Whitelist an app

The Whitelist an app button opens the Whitelist an application dialog: pick a bot that's on the server (search "Search a bot…") or paste the application ID, choose the covered protections (App additions by default), then click Add.

• From the Security page, the app is added to the draft: save afterwards with the bottom bar.
• From the Anti-Raid page, the app is added right away ("Added to whitelist.").

In the left menu, Configuration group, click Anti-Raid.

1. The System (Enabled / Disabled) and Protections (number of active protections out of 14) counters.
2. The filter bar: group (All, System, Channels, Members, Messages, Server), status (All, Active, Inactive) and search "Search a protection, channel…". These filters only change what's displayed.
3. The Enable Anti-Raid master switch.
4. The anti-raid channels, then the protection groups.

The master switch

Enable Anti-Raid is the master switch (off by default). When it's off, no protection applies, even if ticked: the page shows "Anti-raid is off" and every setting is greyed out.

Channels

Each sanction is also recorded in the member's infractions (viewable with /infractions). The thresholds below are Dispatch.IO's default settings, shared by every server.

These protections act when a member joins. The server owner is never affected.

These protections check every message sent or edited. The server owner is never affected. When a protection fires, the message is deleted, the member gets a warning by direct message and the bot counts the infraction.

Two protections have an extra setting, shown when they are on:

• Channels allowed for links (link protection): tick the channels where links stay allowed ("N channel(s) selected"). Threads in those channels are not included.
• Forbidden words list (forbidden words protection): type a word (50 characters max) then Add or Enter; click a word's cross to remove it. Words are saved in lower case. "This word is already in the list." flags a duplicate.

1. Channels allowed for links.
2. Forbidden words list and its input.

These protections read Discord's audit log to find who performed an action. They target that person, whoever they are: only accounts and roles on the whitelist (with the right scope) are exempt. The bot needs the View Audit Log permission.

"Role removal" means the bot removes the person's roles that have the Administrator permission (for mass bans: their ADMIN and MODO staff roles saved for the server). If the person is a bot with an administrator integration role, it is banned instead of timed out (except for mass bans).

On the Anti-Raid page, any change (switches, channels, minimum age, allowed channels, forbidden words) brings up the Unsaved changes bar at the bottom of the screen:

• Save changes: "Anti-raid configuration saved successfully!".
• Reset: goes back to the saved values.

On the bot side, everything is immediate:

If another administrator saves while you have the page open, it updates and shows "Anti-raid configuration updated by …" or "Security updated by …". All these changes also show up in Configuration Logs (Security category). See Synchronisation with the bot.

Emergency alerts are set in Basic configuration, Emergency Mentions & Alerts section. Whenever a critical log is posted (anti-raid sanctions, raid mode, moderation sanctions, channel or role deletions, critical server changes, blacklist), the bot mentions the chosen recipients in the relevant log channel.

Save with the bar at the bottom of the screen ("Emergency mentions configuration saved successfully!"). The change is immediate and logged in General Server Logs.

Some messages come straight from the server and stay in English whatever the site language.

• Anti-raid and security (module): what the bot does on Discord, messages and logs.
• Server management: the /raid-mode command.
• Channels: log channels.
• Logs: history of configuration changes.
• Permissions and roles