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

# Permissions

> How Vetox decides who can run a command and who can change settings — and the role hierarchy rule that trips most servers up.

There are three separate questions, and they have different answers.

<CardGroup cols={3}>
  <Card title="Can Vetox do it?" icon="robot">
    Depends on the bot's own Discord permissions and where its role sits.
  </Card>

  <Card title="Can this member run it?" icon="terminal">
    Depends on their Discord permissions and your per-command settings.
  </Card>

  <Card title="Can they change settings?" icon="gauge">
    Depends on dashboard access.
  </Card>
</CardGroup>

## Role hierarchy

This causes more confusion than anything else in Discord.

<Warning>
  A bot can only act on members whose **highest role is below its own**. If Vetox sits beneath your moderator roles, it cannot ban, mute, timeout or assign roles to those moderators — no matter what permissions it has.

  The same applies to roles: Vetox can only assign or edit roles positioned **below** its own.
</Warning>

Fix it in **Server Settings → Roles** by dragging the Vetox role near the top.

## Who can run a command

Vetox checks permissions itself rather than hiding commands in Discord's menu. Every command is **visible to everyone**, but only runs for members who are allowed.

A member passes if any of these is true:

| They are                                              | Result         |
| ----------------------------------------------------- | -------------- |
| The server owner                                      | Always allowed |
| A member with Administrator                           | Always allowed |
| Holding a role you granted access to for that command | Allowed        |
| Holding the Discord permission the command requires   | Allowed        |

Each command declares the Discord permission it needs — `/ban` needs Ban Members, `/clear` needs Manage Messages, and so on. These are listed on each [command reference](/en/commands/overview) page.

<Note>
  Because commands are visible to everyone, a member without access will see the command and get a permission message when they run it. This is intentional — it lets you grant access by role rather than being limited to Discord's own permission model.
</Note>

### Per-command overrides

On the **Commands** page you can, for each command:

| Setting               | Effect                                                        |
| --------------------- | ------------------------------------------------------------- |
| **Enabled roles**     | Roles explicitly allowed, even without the Discord permission |
| **Disabled roles**    | Roles explicitly blocked                                      |
| **Enabled channels**  | Restrict the command to specific channels                     |
| **Disabled channels** | Block the command in specific channels                        |

See [command management](/en/server-management/command-management).

## Who can use the dashboard

By default, anyone with **Manage Server** in a Discord server can configure Vetox for it.

On **Max** and above, [Dashboard Permissions](/en/server-management/dashboard-permissions) lets you narrow that — granting specific roles or people access to specific sections only, so a moderator can manage Auto-Mod without also being able to change your billing or premium settings.

## Bot permissions by feature

If you narrowed Vetox's Discord permissions after inviting, these are the ones each area needs:

| Feature area                                | Needs                                       |
| ------------------------------------------- | ------------------------------------------- |
| Moderation                                  | Ban Members, Kick Members, Moderate Members |
| Roles, leveling rewards, self roles, colors | Manage Roles                                |
| Auto-Mod, message cleanup                   | Manage Messages                             |
| Tickets, temp voice, server stats           | Manage Channels                             |
| Logs via webhook                            | Manage Webhooks                             |
| Welcomer images, rank cards                 | Attach Files                                |
| Emoji commands                              | Manage Expressions                          |
| Everything                                  | View Channels, Send Messages, Embed Links   |

<Tip>
  Inviting with Administrator avoids all of this. It is the default the invite link uses.
</Tip>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Vetox will not act on a specific member">
    That member's highest role is above Vetox's role. Move Vetox up.
  </Accordion>

  <Accordion title="A role reward is never given">
    The reward role is positioned above Vetox's role. Vetox can only assign roles below its own.
  </Accordion>

  <Accordion title="A moderator says they lack permission">
    They lack both the required Discord permission and an enabled-role grant for that command. Either give them the Discord permission, or add their role under that command's enabled roles.
  </Accordion>

  <Accordion title="Someone can see settings they should not">
    Anyone with Manage Server has full dashboard access by default. Use Dashboard Permissions on Max or above to restrict it.
  </Accordion>
</AccordionGroup>