Discord Moderation Guide: Warnings, Timeouts, Kicks and Bans
Published 15 Nov 2026
Also available in: Deutsch · Português · Español · Français
Members rarely complain that a moderator was strict. They complain that a moderator was inconsistent: one person gets banned for something another got away with last week. Good moderation is less about having powerful tools and more about using the same tools the same way, writing down what you did, and telling people why. This guide covers all three.
The four tools and what each one says
Each sanction sends a different message. Picking the right one is half of the job.
| Action | What happens in Discord | Can they come back? | Best for |
|---|---|---|---|
| Warning | Nothing technical; it's a recorded notice | Never left | First minor offence |
| Timeout | Can read but can't chat, react or speak in voice, for a set duration (up to 28 days) | Ends automatically | Cooling someone down |
| Kick | Removed from the server | Yes, with a new invite | Fresh start or broken setup |
| Ban | Removed and blocked from rejoining; you can delete their recent messages | Only if unbanned | Serious or repeated harm |
A few practical notes. Timeouts are underused: they stop the disruption immediately without the drama of removal. Kicks are weaker than people think, because anyone with an invite link can rejoin a minute later. Bans are the only action that truly keeps someone out, so reserve them for when you mean it.
Write a punishment guide before you need it
Decisions made mid-argument at 2 a.m. are rarely consistent. Spend twenty minutes with your team agreeing on default responses per rule category. Something like:
- Off-topic or mild spam: warning, then a short timeout.
- Harassment or slurs: timeout of a day or more on the first offence, ban if it continues.
- Advertising via DMs: ban, since it targets members privately.
- Scam links or compromised accounts: ban and delete recent messages; unban later if the owner recovers the account and asks.
Defaults are not rules carved in stone. A moderator can deviate, but they should note why. That single habit removes most accusations of favouritism.
Every action should become a case
A case is a numbered record: who was sanctioned, what action was taken, the reason, the moderator, and the time. Add notes when context matters ("member apologised in DMs", "linked to case 87"). Cases solve three everyday problems:
- Handover. The evening moderator can see what the morning moderator already did.
- Appeals. When someone says "I was banned for nothing", you can look at the record instead of trusting memory.
- Patterns. Three separate warnings from three different moderators tell a story that none of them saw alone.
Write reasons someone else can understand
"Spam" is a bad reason. "Posted the same invite link four times in #general after a verbal warning" is a good one. A useful reason states the behaviour, where it happened and whether there was a previous warning. It takes ten extra seconds and makes reviews and appeals painless.
Let history choose the next step
Once you keep cases, escalation becomes natural. Instead of each moderator deciding from scratch, the member's record does: a third warning becomes a timeout, a fourth becomes a longer one, and so on. Automating this keeps the ladder identical no matter who is on shift.
DMs: tell people what happened and why
Members who know why they were sanctioned are far less likely to repeat it or start a scene. A short message is enough:
You've received a 1-hour timeout in Server Name for repeated self-promotion in #general (rule 4). If you think this was a mistake, open a ticket once it ends.
Keep it calm, cite the rule, give the duration and an appeal path. Two caveats: many people have DMs from server members turned off, so a DM may never arrive, and you should never argue about the sanction in public channels. The case record is your source of truth, not the DM.
Clearing the slate
Old warnings shouldn't haunt someone forever. Decide how long minor warnings stay relevant, for example a few months, and clear them after that. Second chances encourage people to stay and improve rather than leave.
Doing all this with MagnificBot
MagnificBot's moderation module is built around these ideas. You get /warn, /timeout, /kick, /ban (including temporary bans) and /purge, every action is stored as a case you can look up with /case, /warnings shows a member's history and /clearwarn wipes it when they've earned a fresh start. Cases accept notes, and automatic escalation can turn accumulated warnings into stronger sanctions. One detail moderators appreciate: if someone bans or times out a member directly through Discord's own menus, that action is recorded as a case too, so nothing falls outside the history.
Your staff can also get dashboard access through panel roles such as Moderator or Reader, without you handing out extra Discord permissions. Everything here is in the free plan; see our comparison of MEE6, Dyno, Carl-bot and MagnificBot if you're weighing options.
FAQ
Should I kick or ban a troll?
Ban if you don't want them back. A kick only removes them until they use another invite link.
How long should a first timeout be?
Long enough to break the moment: 10 minutes to an hour for disruption, a day or more for targeted abuse.
Do I need to DM people when I sanction them?
It's good practice, not a requirement. Always record the reason in a case, since DMs can fail.
Can I undo a ban?
Yes. Unban the user from Server Settings or with your bot, and add a note to the case explaining why.
Ready to bring consistency to your team? Add MagnificBot from magnificbot.com and set up moderation from the dashboard.
Try MagnificBot for free
All modules included, configured from a web dashboard. No credit card, no time limit.
Add to Discord — it’s free