> For the complete documentation index, see [llms.txt](https://docs.asagi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.asagi.xyz/getting-started/permissions-and-bot-masters.md).

# Permissions & Bot Masters

Asagi uses your Discord permissions and roles to decide which servers you can manage and which actions are available in the dashboard.

Understanding these rules is especially important when several people help manage the same server.

### Who Can Access the Dashboard?

A user can manage a server through Asagi when at least one of the following is true:

* they are the **server owner**;
* they have the Discord **Administrator** permission; or
* one of their roles is configured as an **Additional Bot Master Role**.

The server list labels this access as **Owner**, **Admin**, or **Bot Master**.

### Administrator Roles

Roles with Discord's **Administrator** permission are automatically treated as Bot Masters by Asagi.

You do not need to add these roles manually. The **Administrator Roles** list in Server Settings is read-only and reflects the current Discord configuration.

If you add or remove Administrator permission from a Discord role, Asagi updates access based on the new role state.

### Additional Bot Master Roles

Additional Bot Master Roles let you give dashboard access to trusted staff without giving them the Discord Administrator permission.

To configure them:

1. Open your server in the Asagi Dashboard.
2. Select **Settings**.
3. Open **Bot Masters**.
4. Add the roles that should receive Bot Master access.
5. Save your changes.

> 🎬 **Add Bot Master roles**
>
> See where to find Bot Masters settings and how to assign Bot Master access to a role.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0Hy8ldYgZJ9GQJFAuYLR%2Fuploads%2F10PTIlp2vcr6whhCrvgs%2FHow%20to%20add%20bot%20master%20role.mp4?alt=media&token=d22e435d-3ecd-40d3-b1e3-e4ecb9077edf>" %}

> 🖼️ **Example**
>
> This is how the Bot Masters section looks after roles have been added.

<figure><img src="https://3927572991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0Hy8ldYgZJ9GQJFAuYLR%2Fuploads%2FeSEsf3mLjUQK4GmjjoAz%2Fbot%20masters%20card.webp?alt=media&amp;token=069ac4b9-e645-44cf-b138-1d258cefc3dc" alt=""><figcaption></figcaption></figure>

A role that already has Administrator permission does not need to be added again and is excluded from the Additional Bot Master Roles selection.

### Who Can Manage Bot Master Roles?

Only the following users can add or remove **Additional Bot Master Roles**:

* the **server owner**;
* users with Discord **Administrator** permission.

A user who only has Bot Master access can use the dashboard and configure its plugins, but cannot grant or revoke Bot Master access for other roles.

### Role Hierarchy

Discord's role hierarchy affects which roles a dashboard user can work with.

For users who are not the server owner, roles at or above their highest role are unavailable where hierarchy restrictions apply. This follows Discord's normal role-management model.

The server owner is not restricted by their own role position when selecting normal server roles.

> **Important:** Bot-managed and integration-managed roles are not available for selection, including for the server owner. These roles are controlled by Discord or the integration that created them.

### Asagi's Own Role Position

Your permissions in the dashboard and Asagi's permissions inside Discord are two different things.

Even if you are allowed to configure a role in the dashboard, Asagi must still be able to manage that role in Discord when the feature runs.

For features that assign or remove roles:

* keep Asagi's highest role above the roles it needs to manage;
* make sure Asagi has the required Discord permissions;
* do not use managed roles that Discord does not allow bots to assign.

If Asagi cannot manage a target role, the corresponding action may fail even though the rest of the feature is configured correctly.

### Permission Changes Update Automatically

Asagi listens for relevant server and member changes. If your roles or access level change while the dashboard is open, the dashboard can refresh the available role options and access state without requiring you to sign in again.

If your access is removed entirely, you can be redirected away from that server's settings.

### Common Scenarios

| Situation             | Dashboard access | Can manage Additional Bot Master Roles? |
| --------------------- | ---------------- | --------------------------------------- |
| Server owner          | Yes              | Yes                                     |
| Administrator         | Yes              | Yes                                     |
| Additional Bot Master | Yes              | No                                      |
| Regular member        | No               | No                                      |

### Troubleshooting

#### A role does not appear in a selector

Check whether the role:

* is managed by a bot or Discord integration;
* is above or equal to your highest role;
* still exists on the server;
* was recently changed and the dashboard has not refreshed yet.

#### I became an Administrator but the dashboard still shows old access

Refresh the dashboard if the change does not appear immediately. Asagi normally updates permission and role information when Discord reports the change.

#### I am a Bot Master but cannot edit Bot Master roles

This is expected. Additional Bot Master Roles can only be changed by the server owner or an Administrator.

#### Asagi cannot assign a role I selected

Check Asagi's own role position and Discord permissions. Asagi must be above the role it is trying to manage.

### Where to Go Next

You are now ready to configure individual Asagi features. Use the plugin categories in the sidebar to open the guide for the feature you want to set up.
