Supported actions
Stavent wraps common moderation actions with consistent logging and guardrails so your team can act quickly and review later.
| Action | What it does | Logged fields |
|---|---|---|
| Warn | Creates a case and optionally notifies the user. | Reason, evidence, moderator, timestamp |
| Timeout | Temporarily restricts the user. | Duration, reason, case link |
| Kick | Removes the user from the server. | Reason, moderator, user id |
| Ban | Bans the user with optional prune. | Reason, evidence, appeal link |
Approvals and guardrails
For higher-risk actions (kick/ban), you can require dual approval. Approvals are recorded in the audit log with who approved and when.
Tip
Use approvals for new moderators. You can relax the policy later once trust is established.
AutoMod and signals
AutoMod rules can open cases automatically when signals are detected (spam bursts, repeated mentions, flagged links). AutoMod never bans by default—use progressive enforcement.
Progressive enforcement example
if spam_score >= 0.85:
action: timeout 10m
note: "AutoMod timeout (spam burst)"
else if spam_score >= 0.70:
action: warn
note: "AutoMod warning"Evidence and case notes
Attach message links, screenshots, and internal notes. Evidence is stored with immutable timestamps to support consistent reviews and appeals.
Note
When collecting evidence, prefer Discord message links over screenshots. Links keep context and timestamps intact.