Moderation
Mod-log & cases
Moderation without a paper trail is chaos. ModShield turns bans, kicks, timeouts, warns, notes, and automod hits into numbered cases your team can audit.
- Numbered cases
- Human + automod unified
- Warn escalation policies
- Dashboard + API readable
Why teams turn it on
One case number
Humans and filters write into the same system — “who did what” is not buried in random channel history or conflicting bot logs.
Escalation you configure
Warns can auto-escalate to timeout, jail, or ban on the policy you set — consistent for every moderator, not tribal knowledge.
Public or staff mod-log
Optional channel posts keep the community or a staff-only log informed without screenshot archaeology.
Automation-ready
The same cases surface in the dashboard and via the REST API for your own tools and audits.
How it works
1. Something happens
A mod runs /ban, a filter deletes a scam link, or a warn threshold trips — each path can open or update a case.
2. Case is numbered
The incident gets an ID, actor, target, reason, and source (human vs automation) your team can search later.
3. Log and escalate
Optional mod-log channel posts fire; warn policies can promote to stronger actions automatically.
Real situations
Staff handoff
Night mod warns twice; morning lead sees the case trail and escalates without guessing history.
Automod transparency
Filter hits appear as cases so members (or staff) see that enforcement was systematic, not personal.
External audit
Pull cases from the API into your own compliance or support tooling.
FAQ
Do filter hits create cases?
Automated actions participate in the same pipeline so your log is complete — exact coverage is documented in the setup guide.
Can I browse cases without Discord?
Yes — dashboard lists and the REST API expose recent cases for claimed servers.