Add to Discord
Moderation feels like a problem for later, and there is one specific reason it is not: the first time it matters, you will be handling it live, in public, while annoyed. That is the worst possible moment to be deciding policy — and whatever you decide then becomes the precedent everyone remembers.
Setting it up in advance takes about an hour and mostly consists of writing down what you would have done anyway.
The escalation ladder
Discord gives you four real actions. Knowing what each one is actually for removes most of the difficulty.
| Action | What it does | Use it when |
|---|---|---|
| Delete + a word | Removes the message, says why in the channel or a DM | First time, minor, and the person is probably not being deliberate |
| Warn | A recorded note against the member | Repeat behaviour, or the first time something deliberate happens. The record is the point |
| Timeout | They cannot post or speak for a set period. Expires by itself | Almost every real incident. Stops it now, cools it down, creates no drama |
| Kick | Removes them; they can rejoin with any invite | Rarely useful. It is a message, not a barrier |
| Ban | Removes them and blocks the account from returning | When you mean never |
Timeout is the most underused tool in Discord moderation and the right answer to most situations. It ends the incident without ending the relationship.
Write the ladder down
One line in your rules channel. It does more work than any individual rule, because it is what makes enforcement read as policy rather than mood:
"Warning first, then a timeout, then removal. Slurs, harassment and anything illegal skip straight to removal."
Now every decision is a reference to something published, and the argument shifts from "why did you do that to me" to "was this the thing the rule describes" — which is a far easier conversation.
Automate the boring ninety percent
Most of what needs moderating is not a judgement call. Invite-link spam, mass mentions, walls of caps, the same message in five channels — nobody needs to think about these, and they mostly arrive when nobody is awake.
Handling them automatically buys you three things:
- Consistency. The response is the same at 3am as at noon, and the same for a friend as for a stranger. That is very hard to do by hand and very obvious when you fail.
- Speed. Spam removed in a second does not derail a conversation.
- Attention. Your judgement is spent on the cases that actually need it.
The log
A staff-only channel where actions get recorded automatically. Not because anybody reads it daily — because of one specific moment.
Somebody says "I was banned for no reason", in public, and it sounds plausible. Without a log, you are arguing from memory against someone arguing from grievance. With one, it is a link.
What is worth logging:
- Every moderation action, with who did it and why.
- Message deletions and edits in public channels. The most common "what did they actually say" question.
- Joins and leaves, which is how you spot a raid as it starts.
- Role changes, so an unexpected permission grant is visible.
Warnings that mean something
A warning delivered as a message in a channel is a suggestion. It is not recorded, it cannot be counted, and by the third one nobody can remember whether there were two or four.
A warning system worth having does three things:
- Persists. So "this is your third" is a fact rather than a recollection.
- Does something at a threshold. Three warnings equals a timeout, automatically, at a number you published in advance.
- Is visible to the member. They should be able to find out where they stand without asking a moderator.
Building a team
The most common staffing mistake is promoting friends and regulars as a thank-you. Moderator is a job with a permission attached, not a gift, and treating it as recognition produces a staff list longer than the active-member list with nobody clearly responsible for anything.
- Promoting people as a reward for being nice
- Everyone gets Administrator "for convenience"
- No staff channel — decisions get argued in public
- No written policy, so everyone improvises differently
- Twelve moderators for two hundred members
- Recruiting when there is visible work nobody is doing
- A specific permission list, never Administrator
- A private channel for decisions and handovers
- A written ladder everyone applies the same way
- Two or three who are actually around
The permission list
A moderator needs Manage Messages, Timeout Members, Manage Nicknames and View Audit Log. Add Kick and Ban if you trust them with those specifically; plenty of teams keep Ban for senior staff. That is the whole list, and every item on it is reversible — which Administrator is not.
Why it matters is in roles and permissions: Administrator ignores channel overwrites entirely and includes permissions that do not exist yet.
Things worth agreeing in advance
- Who handles a moderator being the problem. Decide before it happens.
- Whether staff moderate their own arguments. They should not.
- How appeals work. A ticket, answered by someone who was not involved.
- What is a ban and what is a timeout. Not so it never varies — so it varies for reasons rather than by who was on.
Handling a raid
Rare, and much easier if the decisions are made in advance. The shape is always the same: a burst of joins, then coordinated spam or mass mentions.
Raise the verification level
Server Settings → Moderation. The Highest setting requires a verified phone number, which stops nearly all throwaway accounts. Turn it down again afterwards — it is a real barrier for genuine members too.
Pause invites
Discord has a "Pause Invites" control that stops new joins outright. It is the fastest way to stop the problem getting bigger while you deal with what is already inside.
Slow-mode the affected channels
Even a few seconds makes coordinated spam unworkable, and unlike a lockdown it does not stop your actual members talking.
Clean up, then review the log
Bulk-delete the spam and ban the accounts. Afterwards, the join log tells you how they arrived — usually one invite link posted somewhere. Revoke it.
Frequently asked
What permissions should a Discord moderator have?
Manage Messages, Timeout Members, Manage Nicknames and View Audit Log covers almost everything. Add Kick and Ban deliberately. Never Administrator — it ignores channel overwrites, includes permissions that do not exist yet, and lets the holder remove your other moderators.
Should I use Discord AutoMod or a bot?
Both, for different jobs. Discord's AutoMod blocks keywords before the message is posted, which nothing else can do. A bot adds the consequence layer — warnings that count, escalation, and a log that ties actions to reasons.
How many warnings before a ban?
Three is the common default and the exact number matters less than publishing it. What matters more is that warnings expire, so someone is not permanently one mistake away because of a bad week two years ago.
What do I do about someone who is annoying but not breaking rules?
Talk to them, privately, once. Most people adjust and are embarrassed. If it continues, that is a sign your rules are missing something you actually care about — write the rule rather than stretching an existing one, because stretched rules are how moderation starts feeling arbitrary.
Should moderation decisions be public?
The action often is — people notice a message vanish. The discussion should not be. Decide in a staff channel, act, and state the outcome briefly if the channel needs to know. Debating a decision in public turns every incident into a second, larger incident.
How do I stop bots and self-bot spam joining?
Discord's verification levels do most of it. Medium as a standing default, Highest during an active raid. A bot cannot stop an account joining — it can only react afterwards, which is why the platform setting is the one that matters here.
Next
If the rules the ladder refers to are not written yet, there is a set to copy. For the repetitive parts beyond moderation — role assignment, ticket pings, announcements — automation is the next step.