Command roles
Limit which roles can use each Buddy command, or lock a whole category of commands to your staff, and see how it works alongside Discord's own permissions.
On this page
- Before you start
- Set it up
- Settings explained
- How restrictions work
- Commands you won't find in the list
- Examples
- Troubleshooting
- A member with the right role still can't use the command
- Members without the role can still use the command
- "Unable to check command permissions right now"
- My role isn't in the list
- Related
By default, anyone who can see a Buddy command can use it. Command roles let you narrow that down: pick a command (or a whole category) and the roles allowed to use it, and everyone else gets a polite "not allowed" message instead.
Before you start#
Command roles are an extra layer on top of Discord's own command permissions. A member has to pass both:
- Discord's check. Some commands are hidden by Discord unless you have a permission. For example the warn commands need Manage Server, and
/pruneneeds Manage Messages. You can change who sees each command in Server Settings → Integrations → Discord Buddy. - Buddy's command roles. If the command has roles listed here, the member needs at least one of them.
Members with Administrator or Manage Server can always use a restricted command, so you can't lock yourself out.
Some commands also do their own check, whatever you set here. For example the
warn system needs Manage Server or a warn access
role, and /prune needs Manage Messages.
Set it up#
It's under Moderation in the sidebar.
In Restrict one command, pick the Command, choose one or more Allowed roles and click Add.
In Restrict a whole category, pick the Category, choose the Allowed roles and click Add. Buddy adds those roles to every command in the category.
Your command roles lists every command and role pair. Click the trash button to remove one.
You can also manage command roles in Discord: run /setup, choose Command Roles, pick a
command, then select the roles that can use it (deselect a role to remove it).
Settings explained#
| Setting | What it does | Default |
|---|---|---|
| Command | The command to restrict. The list shows each command with its category in brackets. | — |
| Category | Restricts every command in that category at once. | — |
| Allowed roles | Members need any one of these roles to use the command. | — |
| Your command roles | Every restriction you've added. A command with no rows here is open to everyone. | Empty |
How restrictions work#
- No roles listed for a command means no restriction from Buddy.
- One or more roles listed means only members with at least one of those roles (or admins) can use it.
- Category restrictions are a shortcut. They add one row per command, per role, at the time you click Add. Commands added to Buddy later aren't included automatically, and you remove category rows one command at a time.
- Subcommands follow their main command. Restricting
invitecovers both/invite createand/invite stats. - Right-click apps share their command's roles. Warn User and Warn Message User follow
warn; Mute User and Mute Message User followmute. /xpsubcommands are covered by bothxpand the matching standalone command. Restrictingxplimits every/xp ...subcommand; restrictingrankalso covers/xp rank,xpleaderboardcovers/xp leaderboard, and so on. A member must pass every restriction that applies.
Commands you won't find in the list#
A few commands can't be restricted here:
- Commands open to everyone by design, like
/bumpand/spin. - Admin-only commands, like the XP configuration commands, which already need Manage Server or more.
Examples#
Keep the games in check by restricting the Fun category to a Regulars role. Or set
roles per command, like this:
| Command | Allowed roles |
|---|---|
summary | Regulars, Moderator |
apply | Verified |
ticket | Member |
What a member without the role sees (only they can see it):
👁️ Only you can see this • Dismiss message
If you use a verification step, restrict apply and ticket to your verified role so brand-new
accounts can't flood your staff before they've read the rules.
Troubleshooting#
A member with the right role still can't use the command#
- Check Discord's side: is the command hidden for them? Look in Server Settings → Integrations → Discord Buddy and make sure their role is allowed.
- Some commands have their own permission check (for example warn commands and
/prune). Command roles can't grant those permissions.
Members without the role can still use the command#
- Members with Administrator or Manage Server always bypass command roles.
- For
/xpsubcommands, a restriction onxpor on the matching standalone command (for examplerank) both apply. - Make sure the row appears in Your command roles.
"Unable to check command permissions right now"#
Buddy couldn't read your command roles, so it blocked the command to be safe. Try again in a moment. If it keeps happening, contact support.
My role isn't in the list#
Run /setup in Discord and choose Update Channels and Roles for Website, then reload the
dashboard.