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

# Permissions

> Map Staff, Admin, and Management roles for Warden command access.

Before touching other modules, tell Warden which Discord roles map to each staff tier. Commands and approval flows read these roles — they are not tied to Discord's built-in permission names.

See [Commands](/configuration/commands) for which tier can run each command.

## Setup

<Steps>
  <Step title="Open Permissions">
    Run **`/config`** → select **Permissions** from the module menu.
  </Step>

  <Step title="Assign roles">
    Use the role select menus for each tier. You can assign up to **10 roles** per tier.
  </Step>

  <Step title="Save and test">
    Have someone in each tier run a command only their role should access — e.g. Staff tries **`/shift manage`**, Management tries **`/infraction issue`**.
  </Step>
</Steps>

## Role tiers

| Tier           | Purpose                                                  |
| -------------- | -------------------------------------------------------- |
| **Staff**      | Day-to-day moderation, shifts, and application review    |
| **Admin**      | Elevated shift and punishment management                 |
| **Management** | Sessions, infractions, ER:LC linking, and approval gates |

<Note>
  Infraction **Require Approval** sends pending actions to Management. Set those roles before enabling infractions with approval turned on.
</Note>

## How tiers stack

Members with multiple configured roles get the highest tier they qualify for. Server Administrators bypass tier checks for admin-only Discord commands like **`/config`**, but should still hold a Management role if they need management commands without Discord admin.