Moderation — calm, opinionated, mod-friendly defaults.

Actions, in increasing severity

Each action takes a reason (free-text), an optional public note (visible to the member via DM), and an optional internal note (visible to mods only). The reason becomes the audit-log entry; the public note becomes the DM body; the internal note never leaves the dashboard.

• /warn — public warning in chat. No enforcement; logged.
• /timeout — Discord-native timeout. Configurable duration; default 1 hour. Auto-removes when the timer expires.
• /kick — removes from server. No data loss; member can rejoin if they have an invite.
• /ban — Discord-native ban. Optional message-history purge (last 7 days).
• /softban — ban + immediate unban, equivalent to a kick + message purge. Useful when you want the cleanup without the permanent block.

The consequence ladder

A configurable per-server escalation policy. By default: first offence → public warning, second → 1-hour timeout, third → 24-hour timeout, fourth → 7-day timeout, fifth → ban. Mods can deviate from any step at any time — the ladder is a default, not a rail. Severe categories (slurs, doxxing, raids, scam-DM campaigns) skip the ladder by configuration.

The ladder makes mod team consistent without making it rigid. New mods know the floor; senior mods deviate when the situation warrants. Audit log records both the action and whether it deviated from the ladder, so the post-incident conversation has the information it needs.

Audit log — full, free, exportable

Every moderation action gets a row: who acted, who was actioned, what action, when, why, against which message ID. Filter by mod, by member, by action type, by time window. Export to CSV or JSON. Comments on entries — useful when a senior mod wants to leave context for whoever picks up the followup.

On the free tier. The audit log is a baseline of trust — we don't paywall it. Premium adds extra retention (1 year vs 90 days) and cross-server analytics.

Mod notes on members

Pin notes to a member's profile that travel with them across channels. "Repeat first-time offender; warn quickly" or "Their account got compromised last month, double-check before banning". Visible only to mods, never to the member.

The review queue

AutoMod-flagged borderline calls land in the review queue rather than auto-acting. Mods see the message, the surrounding context (5 messages before, 5 after), the layer that flagged it, and one-click actions: dismiss, warn, timeout, ban, escalate. See the AutoMod deep-dive for how the queue fits into the four-layer detection stack.

Bulk operations

For raid cleanup or coordinated-spam response: the dashboard surfaces a bulk-action panel. Select N members from a time-window or by search, action them as a group with one confirmation. Audit log records each individual entry plus a parent "bulk action" row that ties them together for retros.

What it doesn't do

• Doesn't do shadow-bans.Every action is logged + DM'd to the affected member. Invisible enforcement erodes trust.
• Doesn't hide actions from the audited member.They get the DM with the reason, the action, and how to appeal. We don't ship "quiet timeout" modes.
• Doesn't do automatic IP-bans.Discord IDs are the unit. If you need IP-level enforcement you're running a different kind of community than this product is built for.