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

# Role Binds

> Bind roles to keywords so members can toggle them with a single word, organised into categories.

# Role Binds

> Bind roles to keywords so members can toggle them with a single word, organised into categories.

## How it works

A **bind** links a short keyword to a role. Once bound, a member toggles that role on or off just by sending the keyword — no slash command, no reaction. Binds can be grouped into **categories**, and you can delegate who's allowed to use them with manager roles.

Configuration requires **Manage Roles** (or **Manage Server** for managers and categories).

## Add a bind

```bash theme={null} theme={null}
;bind add mod @Moderator
;bind add comp @Competitive gaming
```

<ParamField path="name" type="string" required>
  The keyword members type to toggle the role. Stored lowercase.
</ParamField>

<ParamField path="role" type="role" required>
  The role to toggle. Must be below raze's top role and not a managed/integration role.
</ParamField>

<ParamField path="category" type="string">
  Optional category to file the bind under. Lets you reuse the same keyword in different categories and scope manager permissions.
</ParamField>

<Note>
  Servers are limited to **10 binds**. [Donator](/overview/donator-perks) servers have no limit.
</Note>

## Manage binds

<Tabs>
  <Tab title="Remove">
    ```bash theme={null} theme={null}
    ;bind remove mod
    ;bind remove comp gaming
    ```

    Delete a bind by keyword. Pass the category as a second argument if the bind is in one.
  </Tab>

  <Tab title="List">
    ```bash theme={null} theme={null}
    ;bind list
    ;bind list gaming
    ```

    Show all binds, or just the binds in one category. Uncategorised binds are grouped under their own label. Paginated, 10 per page.
  </Tab>
</Tabs>

## Who can use binds

By default binds are toggled by anyone. Restrict that with manager roles.

<Tabs>
  <Tab title="Global manager">
    ```bash theme={null} theme={null}
    ;bind manager @Moderators
    ```

    Set the role allowed to use bind triggers server-wide. Run it with no role to remove the restriction. Requires **Manage Server**.
  </Tab>

  <Tab title="Category manager">
    ```bash theme={null} theme={null}
    ;bind category manager gaming @Gaming
    ```

    Set a role allowed to manage binds within a single category. Run with no role to remove it. Requires **Manage Server**.
  </Tab>
</Tabs>

## Categories

Categories keep large bind setups organised and let you scope permissions per group.

<AccordionGroup>
  <Accordion title="List categories">
    ```bash theme={null} theme={null}
    ;bind category list
    ```

    Show every category, its manager role, and how many binds it holds.
  </Accordion>

  <Accordion title="Remove a category">
    ```bash theme={null} theme={null}
    ;bind category remove gaming
    ```

    Delete a category along with **every bind inside it** and its manager. Requires **Manage Server**.
  </Accordion>
</AccordionGroup>

<Warning>
  `;bind category remove` deletes all binds in that category, not just the category itself. There's no undo.
</Warning>