How to set up moderation on Discord

New invites ask for everything moderation needs. If SUPREO joined your server before, open Server Settings → Roles, pick the bot's role and grant:

• Kick Members, Ban Members and Timeout Members, for the sanctions.
• View Audit Log, so bans and timeouts done by hand in Discord reach the record.
• Manage Messages, for /purge and for anti-spam to delete what it catches.
• Manage Channels and Manage Roles, for /slowmode and the lockdown.

Then drag the bot's role above the roles of the members it will sanction. Discord never lets a bot act on someone ranked at or above it, and this is the most common reason a ban fails. The dashboard's moderation pages list any permission still missing.

Create a channel such as #mod-log that only your staff can read. On the dashboard, open Moderation → Sanctions and pick it as the Moderation log channel. Every case, every lifted case and every edited reason gets a card there, with the member, the moderator, the reason, the length and whether the member was told.

Three more settings sit next to it:

• Tell the member by DM — on by default. Members who know why they were sanctioned argue less and repeat less.
• Name the moderator in that DM — off by default, so moderators are not harassed for doing their job.
• Require a reason — turn it on. A case without a reason is useless three months later.

By default, Discord shows each command to members with the matching permission: /ban to those who can ban, /warn and /timeout to those who can time out. If your moderators do not have those permissions on their role, add the role to the moderator group on the dashboard's Roles page; SUPREO then lets them use every moderation command.

To fine-tune who sees which command, use Discord's own Server Settings → Integrations → SUPREO. Nobody can sanction the owner, the bot, themselves, or someone ranked at or above them.

Create a second staff-only channel, #reports, or reuse the log channel. On Moderation → Reports, turn on Let members report, pick the channel and, if you like, a role to ping.

Members now report with a right-click on a message or a member, or with /report. Each report is a card with a private thread under it, where staff discuss it. A reported message is copied into the report at once, so deleting it afterwards erases nothing. When several members report the same thing, they join one report instead of flooding the channel.

On Moderation → Anti-spam, switch it on. Six rules come ready, each with a sensible default:

• Flood — 6 messages in 5 seconds: timeout.
• Repeated messages — the same text 4 times in 30 seconds: deleted.
• Same message in several channels — the mark of a hacked account: timeout.
• Mass mentions — more than 5 in one message: timeout.
• Invites to other servers — deleted; your own invites are fine.
• Links — off by default; turn it on with a list of allowed sites.

What trips a rule is always deleted first; then the rule's action follows, and it becomes a case like any other. Your staff, administrators and members with Manage Messages are never checked.

A raid is dozens of accounts joining within seconds to spam every channel. You will not have time to read documentation when it happens, so set this up now. On Moderation → Anti-raid, choose what raid mode does to anyone who joins while it is on — kick them, time them out for 24 hours, or only alert — and how long it lasts before ending by itself.

Then remember two commands:

• /raidmode on turns newcomers away and, if the bot has Manage Server, pauses your invites.
• /lockdown on stops @everyone from writing in every channel. /lockdown off puts each channel back exactly as it was — private channels stay private, read-only ones stay read-only.

With Premium, turn on Detect raids and raid mode starts by itself when a wave arrives (for example 10 joins within 10 seconds), including for the accounts that made the wave.

Five minutes now saves an embarrassing first ban:

• From the test account, right-click one of your messages and report it. The report lands in #reports.
• /warn the test account. It gets a DM with the reason; a card appears in #mod-log.
• /timeout it for 10m. It can no longer write.
• On the dashboard, open Moderation → Sanctions, find the timeout and press Lift. The test account can write again, and the log says who lifted it.
• Run /modview on the test account: its two cases and the report it sent.