Moderation
Moderation gives staff structured tools to warn, mute, kick, ban, and timeout members—with case history, strike rules, and audit-friendly records.
What it does#
Staff run moderation actions through slash commands or dashboard workflows (where available). Each action can create a case entry with reason, moderator, and target. Strike rules optionally escalate repeated warnings to mutes or other outcomes you configure.
Cases help handoffs between moderators and provide context when reviewing appeals. Logging can mirror moderation events to a log channel for transparency.
Dashboard path#
Dashboard → Servers → {Guild} → Moderation
Configure mod log destinations, strike rules, default reasons, and retention behavior. Align staff roles in Discord with who may run destructive commands.
Key settings#
| Setting | Free | Pro |
|---|---|---|
| Warn / mute / kick / ban / timeout | Yes | Yes |
| Case retention | 30 days | Longer history on Pro |
| Case cap | 200 cases | Higher on Pro |
| Strike rules | Up to 3 | More on Pro |
| Mass ban tools | No | Yes on Pro |
Train moderators to always supply a reason—future you (and appeals) will thank you.
Strike rules and culture#
Strike rules automate escalation—for example three warns in seven days triggers a mute. Document thresholds in your mod handbook so members understand consistency. On Free, you can configure up to 3 strike rules; complex ladders may need Pro or manual review.
Cases expire on Free after 30 days with a 200 case cap—export important decisions if you need longer internal records. Pro extends retention for appeals and audits.
Permission alignment#
Discord role permissions still gate who can run /ban or /kick even when AIO registers the commands. Give trusted staff the Discord permissions they need, then train them on case reasons and your strike ladder.
Feature overview: Moderation.