Appeals
Let users request review of strikes and bans. Staff deliberate in a per-server staff-notes channel and decide Approve / Reject / Pending. Approved appeals automatically lift the ban.
What is this?
A specialised case type for users to request review of a strike or ban. When the user clicks an appeal-flagged button, staff see three decision buttons (Approve, Reject, Pending) instead of the normal claim/close flow. Approved appeals automatically lift the ban; rejected ones close with a logged outcome.
Why you might want it
The part of moderation where the user gets a structured say. Without an appeal flow you end up debating bans in DMs forever; with one, the request comes in through a documented channel, staff deliberate in a private staff-notes channel, and the decision is logged. Enable it in the setup wizard or add an appeal-flagged button to an existing panel.
What Appeals Are
An appeal is a special case channel a user opens to request review of a strike or ban. Staff see three decision buttons (Approve, Reject, Pending) instead of the normal claim/close flow. Approved appeals auto-lift the ban; rejected ones close with a logged outcome.
Appeals integrate with the strike and ban system — no manual cleanup after a decision. Outcomes are tracked on the player profile and in the audit log.
The staff-notes Channel
Appeals come with a single per-server staff-notes channel inside your Support Inbox category. It's where staff deliberate on appeals (and other contentious cases) without the user seeing.
- Per-server, not per-case. One channel for all staff discussion across cases.
- Staff-only.
@everyonedenied; staff role read & write. - Auto-created when you turn appeals on in the setup wizard or when you toggle the appeals setting in Settings → Cases.
staff-notes for sensitive context that doesn't belong in the appeal channel itself — e.g. cross-referencing the user's history in another server, or coordinating who's going to make the call.How to Enable
Three ways to add an appeal flow, depending on where you start:
- Setup wizard — Enforcement step has an Allow users to appeal strikes and bans toggle. Turning it on adds an appeal-flagged button to the starter case panel and creates the staff-notes channel automatically.
- Discord —
/support panel→ Add Button → pick the Appeal preset. The bot wires up the appeal flag and applies the defaultAPPprefix and username suffix (app-001-bob). - Dashboard — Cases → edit a panel → Add Button → toggle Appeal button. The form exposes the same
is_appealflag plus the channel-naming fields.
If you didn't enable appeals during setup but want to add one later, you'll also want to manually create or repoint the staff-notes channel under Settings → Cases.
Decision Workflow
When a user clicks an appeal button, the bot creates a private case channel scoped to the user and staff. Staff see three decision buttons:
Auto-removes the active ban (or the punishment being appealed) and closes the case with an “approved” outcome. User notified, transcript saved.
Punishment stays. Case closes with a “rejected” outcome. The appeal cooldown applies before the user can submit again.
Keeps the case open for more info or staff consultation. Returns to one of the other two outcomes when ready.
For the full workflow including form fields, cooldowns, and audit trail, see the Appeal System deep dive.
Appeal Channel Names
Appeal buttons default to APP prefix with username included — app-001-bob, app-002-anna. You can override either field in the button config; see Case Naming.
Cooldown
A rejected appeal triggers a re-submission cooldown so denied users can't spam the same appeal. Set the cooldown duration in Settings → Cases → Appeal Cooldown. Approved appeals don't trigger the cooldown.