> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myprotect-bot.fr/llms.txt
> Use this file to discover all available pages before exploring further.

# Sanction Appeals Workflow

> Self-service member appeals with evidence preservation and staff voting.

# Sanction Appeals Workflow

Fairness and transparency build long-term community trust. MyProtect provides a fully integrated **Sanction Appeals** pipeline, allowing banned or muted members to contest their punishments without flooding staff DMs or creating alt accounts to plead their case.

***

## The Appeals Lifecycle

```text theme={null}
[ User is Banned / Muted ]
           │
           ▼
[ Bot DMs sanction details + Appeal Portal URL ]
           │
           ▼
[ User submits appeal statement ]
           │
           ▼
[ Webhook / Embed dispatched to Staff #appeals channel ]
           │
     ┌─────┴─────────────────────┐
     ▼                           ▼
[ Accept Appeal ]           [ Reject Appeal ]
     │                           │
     ▼                           ▼
[ Auto-Unban / Unmute ]     [ Appeal Marked Denied ]
[ Notify User via DM ]      [ Reason logged permanently ]
```

***

## Key Benefits

* **Prevent Alt-Account Evasion**: Members with legitimate explanations can appeal through official channels rather than violating Discord Terms of Service by creating secondary accounts.
* **Evidence Preservation**: When a sanction is issued, MyProtect captures the offending message snippet or attachment evidence and binds it directly to the appeal ticket.
* **Collaborative Staff Voting**: Enable multi-moderator voting thresholds (e.g., 2 approvals required to grant an appeal) to ensure objective outcomes.
* **One-Click Execution**: Clicking **Approve** directly executes the unban or unmute REST call and invalidates associated penalty records in the database.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.