> ## Documentation Index
> Fetch the complete documentation index at: https://technified.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Appeals

> Let members appeal punishments, and process those appeals with your team.

The appeal system lets members request that a punishment be removed or reduced. You can build separate forms for bans, mutes, warnings, or general cases.

Open **Management > Appeals** in the sidebar.

## Overview

The page shows three stats and a card per form.

| Stat | Description |
| - | - |
| Total Forms | Forms created, out of a max of 10 |
| Active Forms | Forms currently accepting appeals |
| Total Appeals | All appeals across every form |

> [!NOTE]
>
> You can have up to **15 appeal forms** per server, so you can run a separate form per punishment type and platform. See [Limits](https://technified.mintlify.site/limits.md) for all creation limits.

Appeal forms share the same statuses (Active, Paused, Archived) and the same **Public** or **Private** visibility as applications. Private forms stay reachable through their direct URL, which is useful for sharing only in DMs or punishment messages.

## Building an appeal form

Appeals use the same drag and drop **Visual Form Builder** as applications, with the same Build, Logic, and Preview tabs. See [Creating application forms](https://technified.mintlify.site/dashboard/management/applications.md) for field types, pages, and logic. This page covers what is specific to appeals.

### Appeal settings

On top of the standard form settings, appeals add two sections.

> [tab] Appeal type
>
> | Field | Choices | Why it matters |
> | - | - | - |
> | Type | Ban, Mute, Warning, or General Appeal | Drives the badge on the user's My Appeals page and which action auto-action targets |
> | Platform | Roblox or Discord | Where the punishment was issued, so auto-action knows whether to call Discord or the Roblox integration |

> [tab] Appeal actions
>
> | Toggle | What it does |
> | - | - |
> | Auto-action on approval | On approval, automatically unban or unmute the user on the configured platform. Off means approval is just a record |
> | Require original punishment | Force the appellant to link the original ban, mute, or warning ID. Required for auto-action to know what to reverse |

## Recommended setups

> [accordion] Separate forms per punishment type
>
> Create four forms, Ban, Mute, Warning, and General, each with a focused set of questions and the matching Type. This keeps the badge accurate and means auto-action only ever touches the right kind of punishment.

> [accordion] One form per platform
>
> If you moderate Discord and Roblox separately, split forms by platform so you can wire auto-action per side.

> [accordion] A general fallback
>
> Keep one public General Appeal form with "Require original punishment" off, for edge cases your other forms do not cover.

## Processing appeals

Open a form and click **View Appeals**.

### Statuses

| Status | Meaning |
| - | - |
| Pending | Submitted, awaiting review |
| In Review | A staff member is investigating |
| Accepted | Granted, punishment will be lifted or reduced |
| Denied | Rejected, punishment stays |

### Deciding an appeal

**1. Investigate**

Open the appeal and read every answer. Check the original punishment in moderation logs and look at the user's history.

**2. Mark in review**

Set it to In Review while you work.

**3. Accept or deny**

Add an optional message or reason and confirm. The appellant receives a Discord DM.

When you accept an appeal, Technified can automatically unban, unmute, or remove the warning if auto-action is configured on the form.

## Best practices

* Match each form's **Type** to its purpose, since it drives both the badge and the auto-action logic.
* Keep appeals shorter than applications. Three to five sharp questions beat a wall of text.
* Use a generous cooldown (24 hours or more) on ban appeals to discourage spam.
* Configure your moderation log channel before enabling auto-action, so every reversal is recorded.


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