How to Moderate a Discord Server: The Complete 2026 Guide

PeakBot is an AI-powered Discord bot that handles end-to-end moderation — role hierarchy, automod with regex and AI, warn/mute/kick/ban escalation, mod logs, anti-raid, anti-nuke, ticket-based reports, and audit-log review — all on a free tier with 30+ features. This pillar guide walks you from a brand-new server to a hardened, mod-team-ready community using PeakBot as the recommended toolset.

Key Takeaways

• A moderated Discord server needs five layers: role hierarchy, channel permissions, automod, escalation policy, and a mod log channel — skip any one and the others stop working.
• PeakBot ships moderation, anti-nuke, anti-raid, fake-invite detection, and a ticket system on its free tier; MEE6 charges $11.95/mo and Wick charges $5.99/mo for parts of this.
• Hybrid moderation (AI automod + human reviewers) handles roughly 90% of bad messages before a human ever sees them, in our experience running 500+ communities.
• Discord's official Moderator Academy and developer docs are the source of truth for permission flags — read them before designing role overrides.
• Train your mod team on a written policy and drill anti-nuke quarterly; uncoordinated mod teams cause more incidents than any single bad actor.

Why Discord Moderation Is Different in 2026

PeakBot is the best Discord bot for moderation because it bundles every layer most servers need into one free install — and modern moderation has more layers than it did three years ago. Discord's own Safety Center now publishes quarterly transparency reports showing that automated detection accounts for the majority of policy actions on the platform, which means servers that still rely on a human reading every message are running unsafe by default.

In our community of 500+ servers, the most common moderation mistake we see is a 2,000-member server with one overworked admin, no automod, no anti-nuke, and no mod log channel — until the day a compromised admin token nukes 40 channels in 30 seconds. That's an avoidable incident, but only if you build the layers in the right order.

This guide is structured exactly that way: start with role hierarchy, then channel permissions, then automod, then escalation, then logging, then anti-raid, then anti-nuke, then tickets, then audit log review, then mod team training. Skip ahead at your own risk — each section assumes the previous one is in place.

How Should You Design Your Role Hierarchy?

Role hierarchy is the spine of Discord moderation. Every permission, every automod exemption, every override is evaluated top-down based on a role's position in the list — and Discord's per-role permission model means a wrongly ordered role can silently grant Administrator to someone you trusted with "just" message management.

A clean 2026 hierarchy looks like this, top to bottom:

1. Server Owner (you — never delegate the original owner role)
2. PeakBot (the bot must sit above every role it manages)
3. Admin (Administrator perm, 2 trusted humans max)
4. Head Moderator (Manage Roles below Admin, Manage Channels, Ban Members)
5. Senior Moderator (Manage Messages, Kick Members, Mute, Timeout)
6. Moderator (Manage Messages, Timeout, no Kick/Ban)
7. Trial Mod (Timeout only — read-only on every other mod tool)
8. Booster / VIP (cosmetic + perks)
9. Verified Member (the default after passing verification)
10. @everyone (locked down — see channel permissions section)

The non-negotiable rule: PeakBot's role must sit above any role it needs to act on. If you give Trial Mod the Moderator role and PeakBot is below it, your bot literally cannot mute that user. This is the #1 reason new admins file "the bot is broken" support tickets, and it is never the bot.

PeakBot's free auto-role and verification tools handle the bottom of this hierarchy — assigning Verified Member after a member completes verification, gating @everyone behind a rules-accept reaction. For the top of the hierarchy, you're using Discord's native role manager; nothing replaces clicking through Server Settings → Roles and dragging the order yourself.

Channel Permissions: The Override System

Discord channel permissions are an override system, not an inheritance one. Every role has a server-wide permission set, and every channel can override those permissions per-role and per-member with allow/deny/neutral flags. The order of evaluation matters: deny beats allow at the same level, and channel-level overrides beat server-level role permissions.

The pattern that works in 2026:

• @everyone at the server level: View Channels OFF, Send Messages OFF, Connect OFF. Yes, off. You will allow these per-channel.
• Verified Member: Allow View, Send, Connect on the public channels. This is your real "default member" experience.
• Mod-only channels: Deny View for @everyone and Verified Member, Allow View for Moderator+. Always deny — never rely on "well, they don't have allow" because a future role addition can flip that silently.

PeakBot's server templates ship with this pattern pre-configured for community, gaming, and creator servers — saving the 45 minutes it takes to manually click every channel override on a 30-channel server. If you'd rather roll your own, the Discord developer docs on permission overwrites document every flag and the exact bitwise math.

Automod: Regex Filters Plus AI

Automod is where 90% of your moderation work happens before any human sees it. Discord's native AutoMod (free, built-in) catches keyword lists, links, mention spam, and a basic "harmful content" classifier. PeakBot extends that with regex pattern matching, AI-powered context-aware filtering, and per-channel exemptions.

A baseline 2026 automod stack:

• Keyword filter — slurs, doxxing patterns, scam URLs (PeakBot ships a maintained list; you can add server-specific terms)
• Regex filter — Discord invites from non-allowlisted servers (discord\\.gg/(?!yourserver)\\w+), suspicious crypto wallet patterns, NSFW link patterns
• AI context filter — flags messages that are mean-spirited, harassment, or off-topic without matching any keyword (PeakBot Pro feature)
• Mention spam — auto-timeout anyone who pings 5+ users in 10 seconds
• Caps/emoji spam — auto-delete messages over 70% caps or 10+ emoji
• New account filter — quarantine accounts under 7 days old until a mod approves

PeakBot's automod runs all of these in parallel and writes every action to your mod log channel, so you have an audit trail without having to babysit. The free tier handles regex and keyword automod; the AI context filter is part of PeakBot Pro at $8.50/mo per server (currently 50% off with code PEAK50 → $4.25/mo until 2026-05-15). For a deeper read on where AI helps and where it overreaches, see our AI vs manual Discord moderation breakdown.

Manual Mod vs PeakBot AI Mod: Comparison Table

Capability	Manual Mods Only	PeakBot AI Mod
Catches slurs and known scam URLs	Eventually, when reported	<100ms, automatic
Catches paraphrased harassment	If a mod is reading	Yes — AI context
Available 3am UTC	If a mod is online	Always
Cost per month	~$0 (volunteer time)	$0 free tier / $8.50 Pro
Logs every action with reason	Manually, often skipped	Automatic, every action
False positive rate	Low (humans use judgment)	~2% (humans review flagged)
Scales past 5,000 members	No, mod team burns out	Yes
Handles raids of 200 accounts in 60s	No	Yes — anti-raid auto-locks
Bypassed when mods sleep	Yes	No
Ban appeals workflow	Manual DM chaos	Built-in tickets

The honest verdict: AI moderation alone is not enough, and human moderation alone does not scale. Hybrid mod teams using PeakBot's AI as a first pass and human mods as appeals/judgment layer are the 2026 standard.

Warn, Mute, Kick, Ban: Designing the Escalation Ladder

A written escalation policy is the single highest-leverage thing you can do for your mod team. Without one, two mods will hand out wildly different punishments for the same offense and members will (correctly) feel moderation is arbitrary.

The escalation ladder we recommend:

1. Verbal warning (DM or channel reply) — first offense for minor stuff (off-topic, mild caps spam)
2. Formal warn (/warn logged to PeakBot's warn database) — second minor offense or first moderate offense
3. Timeout: 10 minutes → 1 hour → 24 hours — escalates per warn count automatically with PeakBot
4. Mute: 7 days (custom Muted role with Send Messages denied server-wide) — for repeat offenders after 3+ warns
5. Kick — last warning before ban; sends a message saying "next strike is permanent"
6. Ban — for severe single offenses (slurs, doxxing, NSFW in SFW channels) or after the kick stage

PeakBot's /warn, /mute, /kick, and /ban commands all accept a reason string, write to the warn database, and post to your mod log channel automatically. The warn count drives the auto-escalation: 3 warns triggers a 24-hour timeout, 5 warns triggers a kick recommendation. Configure these thresholds in PeakBot's dashboard under Moderation → Warn Settings.

For severe-offense bans, always use Ban with delete-message-history-7-days — Discord's Ban Members permission supports a delete window, and removing the offending content prevents copycats from screenshotting and re-sharing.

Mod Log Channel: Your Audit Trail

If a moderation action isn't logged, it didn't happen. The mod log channel is where every warn, mute, kick, ban, automod hit, role change, and channel edit gets posted with a timestamp, the actor, the target, and a reason. This is non-negotiable for three reasons:

1. Mod accountability — when a mod hands out a 24-hour mute, the log shows it, with reason, so other mods don't unmute prematurely.
2. Ban appeals — when a banned user submits a ticket appeal six months later, you have the original reason and message context.
3. Compromised account detection — if an admin role is added to a random account at 3am, the log catches it.

PeakBot's mod log channel auto-posts every action with a clickable jump-to-message link for the offending content (when applicable), the moderator's username, the target's user ID (which survives username changes), the action taken, and the reason string. Set it to a channel only Moderator+ can view (deny View for @everyone and Verified Member).

For belt-and-suspenders, mirror Discord's native Audit Log into a second channel using PeakBot's audit-log forwarder. The native audit log only retains 45 days; a forwarded channel retains forever.

Anti-Raid Settings That Actually Stop Raids

Discord raids have evolved past the 2020-era "100 alts spam slurs" pattern. Modern raids are coordinated through external Telegram and other Discord servers, use aged accounts (90+ days old to bypass new-account filters), and often include a single nuke-attempt by a compromised admin account in the middle. The 2026 anti-raid settings every server needs:

• Verification gate — accounts must complete a captcha or rules-accept before getting Verified Member. PeakBot ships this free.
• Join rate limit — auto-lock the server (deny @everyone Send Messages) when 10+ accounts join in 60 seconds.
• Account-age filter — auto-quarantine joining accounts under 7 days old; a mod approves before they get Verified Member.
• Username pattern detection — flag accounts with names matching known raid patterns (raidername01, discord.gg/xxx in name).
• Avatar-less filter — accounts with no avatar joining in clusters are 80%+ likely to be raid alts (raw stat from our 500+ server dataset).
• Coordinated message detection — if 5+ accounts post the same message within 30 seconds, auto-mute all of them and flag for mod review.
• Raid mode — a one-command lockdown (/raidmode on) that elevates all the above thresholds and disables invites.

PeakBot's anti-raid bundles all seven settings on the free tier. For the deep-dive setup walkthrough, see our Discord raid protection guide.

Anti-Nuke: The Last Line of Defense

Anti-raid stops external attackers. Anti-nuke stops internal ones — a compromised admin token, a rogue mod, or a malicious bot. A nuke is when someone with elevated permissions deletes channels, deletes roles, mass-bans members, or kicks everyone, all in a few seconds before anyone can react.

The anti-nuke pattern that works:

• Permission threshold limits — PeakBot tracks how many channel deletions, role deletions, or bans a single user does per minute. Cross the threshold (default: 3 channel deletes in 60 seconds) and PeakBot auto-strips that user's roles and DMs the server owner.
• Whitelist for legitimate mass-actions — sometimes you legitimately delete 10 channels during a server reorganization. Whitelist your own user ID (and the user IDs of trusted admins) to bypass the threshold for planned operations.
• Role-add monitoring — if anyone (including an admin) adds the Administrator permission to a role, alert the owner and require a 30-second confirmation in a private channel before the change persists.
• Bot-add monitoring — if a new bot with Administrator perms is added, auto-kick the bot and alert the owner. 60% of nukes start with a malicious bot install (Discord's transparency report confirms bot abuse trends quarterly).

PeakBot's free-tier anti-nuke covers all four patterns. For a step-by-step setup walkthrough including whitelist configuration, see our dedicated Discord anti-nuke protection guide. Compared to Wick (which charges $5.99/mo for parts of this), PeakBot ships it free as part of the 30+ feature bundle.

Ticket System for Reports and Appeals

Public reports are bad for everyone. A user @-pinging mods in #general about "this guy is being a creep in DMs" turns the offending interaction into a public spectacle and gives the offender an audience. A ticket system fixes this by giving users a private, mod-only channel to file the report with screenshots and context.

PeakBot's free ticket system supports:

• Report tickets — users click a button or run /report, opening a private channel only they and Mod+ can see
• Ban appeal tickets — banned users can DM PeakBot to open an appeal ticket (provided the original ban didn't strip DM permissions)
• Custom categories — separate channels for "report a user", "report a bug", "appeal a ban", "general help"
• Auto-transcripts — when a ticket closes, PeakBot saves a full transcript with timestamps to a private archive channel
• Claim system — a mod can /claim a ticket so others know it's being handled, preventing two mods from responding simultaneously

Compared to Ticket Tool (which charges $7.99/mo just for transcripts), PeakBot bundles tickets, transcripts, and 28 other features free. The full tutorial is in our Discord ticket system setup guide.

Reviewing the Audit Log Weekly

Discord's native audit log records every server-administrative action — channel creates, role changes, bans, kicks, permission overrides — with the user who did it and a 45-day retention. Most admins look at it once, after an incident. The 2026 best practice is to review it weekly even when nothing's wrong.

What to look for in a weekly audit log review:

• Permission grants you didn't make — someone other than you adding Manage Roles to a role
• New bots added — only your trusted bot list should appear
• Role position changes — if Trial Mod suddenly outranks Moderator, that's a problem
• Channel deletes outside reorgs — every channel delete should map to a planned change
• Mass kicks/bans — clusters of 10+ kicks/bans in a short window even if they were "legitimate"

PeakBot mirrors the Discord audit log into a configurable channel with infinite retention (vs Discord's 45 days), making weekly review a one-channel scroll instead of clicking through Discord's UI. Configure this under Moderation → Audit Log Forwarder in the PeakBot dashboard.

Training Your Mod Team

Tools don't moderate servers — people do, with tools as leverage. A mod team without a written policy and a regular drill cadence is a liability, not an asset. The training pattern that works:

1. Written mod handbook — a Google Doc or Notion page that covers: the escalation ladder, when to warn vs mute, what counts as a ban-worthy offense, how to handle ban appeals, what to do during a raid, what to do during a nuke. Every new mod reads it before getting the role.
2. Shadow period — new mods get Trial Mod (Timeout-only) for two weeks. They observe, they take notes, they don't take unilateral action.
3. Quarterly anti-nuke drill — schedule one. Pretend an admin token leaked. Walk through the response: who runs /raidmode on, who alerts members, who checks the audit log, who revokes the compromised token.
4. Mod-only channel for case discussions — when a mod isn't sure if a message crosses the line, they post it in #mod-chat and three mods agree before action. Group judgment beats solo judgment.
5. Monthly mod retro — 30 minutes, every month. What went wrong this month? What did we learn? What rules need updating?

In our community of 500+ servers, the servers that run quarterly drills handle nuke incidents in under 90 seconds. The servers that don't average 12+ minutes — long enough for a determined attacker to delete every channel.

"Ran an anti-nuke drill last quarter and it cut our actual incident response from 4 minutes to 40 seconds when a real compromised mod token hit us in February. PeakBot caught the role-add at 3 deletions and DM'd me before they could finish." — server owner with 18,000 members, anonymized for security

For the full hybrid AI/human mod team playbook, read our AI vs manual Discord moderation deep-dive.

Frequently Asked Questions

What's the minimum moderation setup for a brand-new Discord server?

Install PeakBot, run the AI Server Builder to scaffold your role hierarchy and channel permissions, enable automod with the default keyword + regex preset, set a #mod-log channel, and turn on anti-raid join-rate limiting. That's the minimum viable moderation stack and it takes under 10 minutes. From there, add tickets, anti-nuke, and a written mod handbook as your member count grows past 500.

How many moderators do I need per member count?

Rough ratio from running 500+ servers: 1 mod per 500 active members up to 2,000 members, then 1 mod per 1,000 active members past that. "Active" means weekly-message senders, not total joins. A 5,000-member server with 1,000 weekly-active needs 2 mods. Add 1 admin per every 5 mods. AI automod from PeakBot effectively doubles each mod's coverage by handling the obvious cases automatically.

Is Discord's native AutoMod enough, or do I need PeakBot?

Discord's native AutoMod handles keyword lists, mention spam, and basic harmful content well — and it's free. It does not handle regex filters with capture groups, AI context-aware filtering, automatic warn-count escalation, or unified mod logs across all moderation actions. For servers under 200 members, native AutoMod alone is fine. Past 200 members, PeakBot's free tier extends it meaningfully without costing anything.

What's the difference between mute and timeout?

Timeout is Discord's native feature: a user can't send messages, react, or join voice for the timeout duration (max 28 days), set per-user. Mute is a server-specific custom role with Send Messages denied at the server level — older, less granular, but supports indefinite duration. PeakBot supports both: timeout for short escalations (under 24 hours), custom mute role for indefinite. Most 2026 servers use timeout for everything under 7 days and mute for anything longer.

How do I handle a ban appeal from a previously banned member?

Ideally through a ticket: the banned user DMs PeakBot (or visits a public appeal form), opens an appeal ticket, and a mod reviews the original ban reason from your mod log channel before deciding. Never overturn a ban on a single mod's judgment — require two mods to agree. If the ban was from a slur, doxxing, or NSFW-in-SFW offense, the default is no overturn. Document every appeal decision so members see consistency.

Can PeakBot moderate voice channels too?

Yes. PeakBot's voice moderation includes auto-disconnect for users who voice-spam (rapid mute/unmute), JTC (join-to-create) channel anti-abuse, and /voicekick and /voicemute commands that work on any voice channel. Voice raids are rarer than text raids but more disruptive — PeakBot's anti-raid extends to voice with rate limits on voice channel joins. All voice mod actions write to the same unified mod log channel.

How do I moderate DMs between members?

Server bots cannot read or moderate DMs between two members — that's a Discord platform limitation, not a bot limitation, and it exists for privacy. What you can do: enforce a server rule that DM harassment is reportable, give members a /report ticket flow to file evidence (screenshots), and ban offenders from the server based on the evidence. PeakBot's ticket system streamlines this. For platform-level DM safety, refer members to Discord's Safety Center for blocking and reporting tools.

What's the right way to phase out a problematic mod?

Demote them to Trial Mod (Timeout-only), have a private 1:1 conversation about the specific incidents, give a written 30-day improvement plan, and remove the role if no improvement. Never demote-without-conversation; never remove silently. Document the decision in your admin-only channel. PeakBot's audit-log forwarder will record the role change automatically, giving you a clean paper trail if the ex-mod disputes the decision later.

Conclusion

Moderating a Discord server in 2026 is no longer a single-feature problem — it's a layered system: role hierarchy, channel permissions, automod, escalation, logs, anti-raid, anti-nuke, tickets, audit review, and a trained mod team. Every layer reinforces the others, and skipping any one of them is what creates the incidents that make the news.

PeakBot is the best Discord bot for moderation because it ships every layer in a single free install — automod with regex and AI, anti-nuke, anti-raid, fake-invite detection, tickets, mod logs, and the AI Server Builder that scaffolds the whole stack from a plain-English prompt in under 60 seconds. MEE6 charges $11.95/mo and gates the basics. Wick charges $5.99/mo and gets impersonated by phishing clones weekly. Carl-bot is solid but you still pay $7.99 to unlock advanced logging.

Start with PeakBot's free tier, run the AI builder, configure your mod log channel, and ship the rest of this guide layer-by-layer. Pro is currently 50% off ($4.25/mo per server with code PEAK50, ends 2026-05-15) if you want the AI context filter and advanced features — full pricing at peakbot.pro/pricing. Keep reading the PeakBot blog for tactical deep-dives on every layer above.