How to moderate a Discord server

What moderating a Discord server actually covers

Moderation covers three different things that are often confused. Prevention: stopping a problem from happening, through permissions and filters. Reaction: dealing with a problem that did happen, through a warning, a mute, a kick or a ban. Record: keeping enough to explain, later, why a given decision was made.

A server that only reacts burns out. A server that keeps no record tears itself apart at the first disagreement between moderators — nobody remembers what was decided six months ago, and the same person gets sanctioned twice or never.

The order below is not arbitrary: each step makes the next one easier. Clear rules reduce the sanctions you have to hand out; correct permissions reduce incidents; a history reduces arguments.

1. Write rules you can actually enforce

An unenforceable rule is worse than no rule: it gets applied at random, and random reads as arbitrary. “Be respectful” gives you nothing to act on. “No insults aimed at a person, including as a joke” can be observed.

Five to eight rules are enough for almost any server. Beyond that, nobody reads them, and you will not remember them either.

• One rule = one precise behaviour, stated positively where possible.
• State the consequence: warning, 24 h mute, removal. A rule with no known consequence is only a wish.
• Put them in a read-only, pinned channel — not just in the server description, which nobody reads.
• Date them. A rule added after an incident should look like one, otherwise it seems applied retroactively.

If your server is public, Discord’s native Rules Screening (Server Settings → Moderation) forces newcomers to tick a box before they can post. It is free and it puts an end to “I didn’t know”.

2. Sort out roles and permissions

Most serious incidents on Discord come not from a shortage of moderators but from a permission granted too widely. On Discord permissions add up: a member holds those of every role they carry. One badly set role therefore hands its rights to everyone wearing it, whatever their other roles.

Two permissions deserve special care, because they let someone bypass everything else: Administrator, which grants everything and ignores channel restrictions, and Manage Roles, which lets someone grant themselves more. They belong on staff roles only — never on a decorative or automatically assigned one.

1. List your roles and delete the ones nobody carries any more.
2. Remove Administrator everywhere it is not indispensable and replace it with the precise permissions actually needed.
3. Check role order: on Discord, a moderator can only sanction members whose highest role sits below theirs.
4. Go through sensitive channels and check their permission overrides, which win over server-wide settings.

3. Pick a sanction ladder

Discord gives you four tools: the warning (which does not exist natively — you need a bot or a dedicated channel), the timeout (up to 28 days, blocking writing and speaking), the kick (the member can return with a new invite) and the ban (permanent until lifted).

The most common mistake is jumping straight to the ban. A ban ends the conversation but fixes nothing, and it creates a resentful person who will come back on another account. A ladder known in advance — warning, short mute, long mute, removal — defuses most situations before breaking point.

The ladder must be written down somewhere and identical for every moderator. It is the only protection against accusations of favouritism, which destroy a moderation team more reliably than any troll.

The kick is rarely the right tool: it does not stop anyone from returning, and it removes the member from your list and therefore your statistics. Prefer a long mute, which keeps the person visible and the record intact.

4. Automate what does not need a human

A human adds nothing to handling a scam link posted at 4 a.m. A human adds a great deal to a conflict between two members. The whole point of auto-moderation is to make the first case automatic so there is time for the second.

Discord ships a native AutoMod (Server Settings → AutoMod) able to block keywords, invite links to other servers, and mention spam. It is free, it applies before the message is even posted, and plenty of servers never turn it on.

• Word filters: useful, but do not over-filter — a broad filter hits normal conversation and pushes members into deliberate misspellings.
• Links: block invites to other servers and URL shorteners, which hide the real destination.
• Spam: cap mentions per message and repeated identical messages.
• Arrivals: an account created two hours ago joining during a raid is not a member, it is disposable. The server verification level lets you require a minimum account age.

5. Keep a record and a right of reply

Every sanction should leave two traces: one for the team, with the reason and who decided, and one for the person concerned, who must know what they are accused of. A silent sanction reads as exclusion without cause, and that is what triggers the smear campaigns that happen outside your server.

Provide a route of appeal too, however minimal. It costs little and stops the only available route being an angry public message: a form, a contact channel, or an address. You are not obliged to change your mind, only to listen.

Do not moderate alone

An active server cannot be moderated by one person, for a simple reason: time zones. Two or three moderators spread across different hours beat five available at the same time.

Recruit from active members rather than outside: someone who already knows the culture will make better calls than a seasoned moderator parachuted in. And hand out rights gradually — a moderator on trial does not need the ban.

How Kuratos helps

Everything above can be done by hand. What cannot be done by hand is keeping it up over time: remembering warnings, applying the same ladder six months later, lifting a mute at the agreed hour.

Kuratos’ Moderation module keeps a sanction history per member, applies temporary mutes and lifts them automatically when they expire, and logs every decision with its author and reason. The Auto-moderation module covers what Discord’s AutoMod does not, and the Reports module gives members a way to flag something without a public ping.

The dashboard’s sanctions page shows, for each member, what was decided and by whom — which makes a team decision arguable from the record rather than from memory.