> ## 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.

# Command management

> Enable, disable and restrict any of Vetox's commands per role and per channel, and set preset moderation reasons.

The **Commands** page lists every Vetox command and lets you control each one individually.

## The list

Five tabs, each showing a live count: **All**, **General**, **Moderation**, **Info** and **Leveling**. Each card shows the command name, its description, its category, an on/off switch and a **Manage** link.

A search box filters across every tab.

<Note>
  Toggling a command on the list is **held locally until you save**. Toggling it back to its original state clears the change entirely — the save bar disappears on its own.
</Note>

## Per-command settings

Open **Manage** on any command.

| Setting                                     | Default | Effect                                                       |
| ------------------------------------------- | ------- | ------------------------------------------------------------ |
| **Enabled**                                 | On      | Turn the command off entirely                                |
| **Command Aliases**                         | None    | Alternative names for the command                            |
| **Enabled Roles**                           | None    | Roles allowed to use it, even without the Discord permission |
| **Disabled Roles**                          | None    | Roles blocked from using it                                  |
| **Enabled Channels**                        | None    | Restrict it to specific channels                             |
| **Disabled Channels**                       | None    | Block it in specific channels                                |
| **Auto-delete command invocation**          | Off     | Remove the member's command message                          |
| **Auto-delete with message deletion**       | Off     | Remove Vetox's reply when the member deletes theirs          |
| **Auto-delete bot's reply after 5 seconds** | Off     | Clean up the response automatically                          |

<Note>
  **Enabled Roles is the useful one.** It grants access to a role that does not hold the underlying Discord permission — letting a Trial Moderator role use `/warn-add` without giving them Manage Messages across your whole server.
</Note>

## Subcommands

Commands with subcommands — `/ticket` and `/starboard` — can be configured at the individual subcommand level, so you can allow `/ticket close` for all support staff while restricting `/ticket merge` to seniors.

<Warning>
  **Subcommands support fewer options.** Aliases, auto-delete invocation and auto-delete with message deletion are all unavailable and appear disabled with a note saying so.

  A subcommand can set: enabled, role restrictions, channel restrictions and auto-delete reply. Everything else is configured on the parent command.
</Warning>

<Note>
  [Dashboard Watcher](/en/server-management/dashboard-watcher) records subcommand changes under the **parent** command's name. An audit entry for `/ticket` may actually be a change to one of its subcommands.
</Note>

## Preset reasons

Five moderation commands support preset reasons: **`/ban`**, **`/mute-text`**, **`/mute-voice`**, **`/warn-add`** and **`/timeout`**.

When a moderator runs one of these **without** typing a reason, Vetox shows a menu of your defined reasons instead of leaving the field blank.

Four of them — `/ban`, `/mute-text`, `/mute-voice` and `/timeout` — also let each preset carry a **duration**, so choosing "Spam — 24 hours" applies both at once.

<Tip>
  Preset reasons make moderation logs far more useful. Free-typed reasons vary between moderators and are hard to search later; a fixed list keeps them consistent and lets you filter on them.
</Tip>

<Note>
  The reason list has no reordering — new entries are appended. Deleting a middle entry re-renders the rows beneath it, so double-check before saving.
</Note>

## Common patterns

<AccordionGroup>
  <Accordion title="Keep fun commands out of serious channels">
    Add your announcement and support channels to **Disabled Channels** for `/roll`, `/translate` and similar.
  </Accordion>

  <Accordion title="Give trial moderators limited powers">
    Add the Trial Moderator role to **Enabled Roles** on `/warn-add` and `/timeout` only. They gain those commands without gaining the Discord permissions.
  </Accordion>

  <Accordion title="Confine bot spam to one channel">
    Set **Enabled Channels** on `/rank`, `/top` and `/profile` to a single bot channel.
  </Accordion>

  <Accordion title="Turn a command off entirely">
    Switch **Enabled** off. It stops working for everyone, including administrators.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="My change did not apply">
    The list page holds toggles locally until you use the save bar. Check you saved.
  </Accordion>

  <Accordion title="A moderator still cannot use a command">
    Enabled Roles grants the command, but Vetox still needs its own Discord permission to carry out the action, and the role hierarchy still applies. See [Permissions](/en/permissions).
  </Accordion>

  <Accordion title="Aliases are missing on a subcommand">
    Expected — aliases are configured on the parent command only.
  </Accordion>

  <Accordion title="Preset reasons are not offered">
    Only five commands support them. The moderator must also run the command without typing a reason.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Command reference" icon="list" href="/en/commands/overview">
    Every command, its options and the permission it requires.
  </Card>

  <Card title="Permissions" icon="user-lock" href="/en/permissions">
    How Vetox decides who may run a command.
  </Card>
</CardGroup>