Dashboard Guides
Last updated Sep 27, 2026Open in dashboard

Roles and Permissions

The bot decides who may do what with a few simple rules. This page explains them, shows where to set your staff and admin roles, and walks through the Permissions page, which checks the bot's own permissions.

The access model

LevelWho has itWhat it unlocks
OwnerThe bot's owners, as set by whoever runs the bot (normally the owner of its Discord application).Everything, in every server, including owner-only tools.
AdminThe server owner, members with the Administrator permission, and members with one of your Admin Roles. Owners count too.Commands marked Admin, plus everything staff can do.
StaffMembers with Manage Server or one of your Staff Roles, plus every admin.Commands marked Staff.
Dashboard accessMembers with the Manage Server permission (which includes Administrator and the server owner), and the bot's owners.Opening this server's dashboard and changing its settings.

Two points often cause confusion:

  • Staff and admin roles never give dashboard access. Someone with a staff role but without Manage Server can use staff commands in Discord but cannot open the dashboard.
  • Some commands check a Discord permission instead of a role. Most moderation commands, such as /ban, /kick, /timeout and /warn, need the matching Discord permission (Ban Members, Kick Members, Timeout Members). Each module's commands page lists what every command needs in its Permission column.

Set staff and admin roles

Staff and admin roles are set on the Settings page, in the Permission Roles card.

Permission Roles on the Settings page
  1. Open Settings in the sidebar. Open Settings
  2. In Permission Roles, open Staff Roles or Admin Roles.
  3. Search for a role and click it to add it. Click it again, or the x on its chip, to remove it.
  4. Click Save Changes.
Pick roles from the searchable list

Staff roles

Give staff roles to your moderators and helpers. Members with one of them can use commands marked Staff (for example /clean, the mass moderation commands and /form link), provided they also have any Discord permission the command lists.

Admin roles

Give admin roles to members you trust with the bot's admin commands, such as /xp add, /xp reset and /activity reset. Members with Administrator are always admins, so you do not need an admin role for them.

Important

Only a member with Administrator (or the server owner) can change the Staff Roles and Admin Roles lists, because they decide who counts as staff. The @everyone role cannot be added.

Limit commands with Discord's Integrations settings

Discord has its own per-command permissions, and they work together with the bot's checks: a member must pass both.

  1. In Discord, open Server Settings > Integrations and select the bot.
  2. Choose a command and set which roles, members and channels may use it.

Many admin and moderation commands are hidden by default from members without the matching permission (for example Manage Server or Ban Members). Discord's overrides can show them to other roles, but the bot still checks its own rules when the command runs.

You can also turn single commands off for the whole server on a module's Commands tab in the dashboard.

The Permissions page

Permissions in the sidebar does not change anything. It shows what the bot itself can do in your server, so you can find out why a feature fails.

Server Permissions on the left, Role Hierarchy on the right

Open Permissions

Server Permissions

The left column lists every Discord permission, grouped into General, Moderation, Text and Voice, with a green check where the bot has it and a red cross where it does not. The bar at the top counts how many it has.

The select at the top reads Server permissions. Pick a channel there to see the bot's permissions in that channel, after the channel's own overwrites. This is how you find a log channel where the bot cannot send messages. Reset to server permissions returns to the server-wide view.

In #mod-logs the bot cannot send messages, embed links or attach files

Role Hierarchy

The right column shows the bot's highest role and its position, then two counts:

  • Manageable members: members whose roles are all below the bot's, so it can moderate them and change their roles.
  • At or above my role: members the bot cannot act on.

Roles at or above me lists every role the bot cannot give, take away or act on. Click a role to see its members.

Click a role to see who has it

Fix a "missing permission" problem

  1. Open Permissions and find the red cross. If the problem is in one channel, pick that channel in the select first.
  2. If the permission is missing server-wide, edit the bot's role in Server Settings > Roles in Discord and turn it on.
  3. If it is missing in one channel, open that channel's Edit Channel > Permissions in Discord and allow it for the bot's role.
  4. If the bot cannot give a role, drag the bot's role above it in Server Settings > Roles, then check that the role left the Roles at or above me list.
  5. Reload the Permissions page to confirm.

Staff logs

Every change made through the dashboard, and every staff or admin action taken with the bot's commands, is recorded in the staff logs, with who did it and when.