Limit a command to staff, keep it in #bot-commands, block a role, or turn it off across the server. Rules can target one command or a whole module.
Before you begin
- You need Manage Server.
- Discortics needs Send Messages and Embed Links for the Discord panel.
Make a command staff-only
This example lets only the Moderator role use /purge.
Allow one role from the Dashboard
- Open Dashboard → Permissions.
- Find Purge and select Manage.
- Open Roles and set the default mode to Deny.
- Add the Moderator role to Allowed.
- Select Apply changes, then save with the save bar.
- Test
/purgewith a moderator and a normal member.
[Insert screenshot here]
The Purge role rule before saving
How rules work
Each command or module has a status and separate rules for users, roles, channels, and categories.
| Default mode | Who passes | Use it for |
|---|---|---|
| Allowed | Everyone except the Denied list | Commands that work almost everywhere |
| Denied | Only the Allowed list | Staff-only commands, a single bot channel |
- Deny always wins. A member with one allowed role and one denied role is denied. An allowed user is still blocked by a denied role, channel, or category.
- Module and command rules both apply. A deny from either one blocks the command.
- Disabled commands are blocked unless a user, role, channel, or category has an explicit allow and nothing denies it.
- Threads follow their parent channel and category.
- Server owners and Discortics owners always bypass these rules.
- Allowing a command doesn't grant Discord permissions. The member still needs any permission the command requires.
Change a rule
- Run
/settings command command:<name>or/settings command module:<name>, or open Dashboard → Permissions and select Manage. - Use the status button to enable or disable the target.
- Open Users, Roles, or Channels. On the Dashboard, use the scope dropdown: Roles is selected first, followed by Channels, Categories, and Users.
- Choose the default mode from the dropdown, then add exceptions. New dashboard rules start at Denied; saved rules keep their mode. On the Dashboard, paste user IDs separated by commas or new lines.
For AntiNuke, Manage opens its dedicated settings, where the server owner and AntiNuke admin roles control access.
For other commands, Manage opens a right-side drawer with Roles, Channels, and Users tabs. The Channels tab contains separate channel and category settings. When managing an individual command, the Roles tab lists its required Discord permissions and matching roles. These summaries are hidden when managing a whole module. Roles added to Allowed while the default is Denied are omitted from that list. Channel and access rules still apply.
Use the Prefix / Slash toggle beside Permissions to display message-command names such as ;accept or registered slash paths such as /application accept. Slash mode shows commands with a slash entry; switching formats keeps permission edits.
The command list and Permissions page use the bot's command modules. Anime, manga, character lookups, and bump are under Info; discovery configuration is under Settings.
Discord changes save immediately. On the Dashboard, select Apply changes, then use the save bar.
Copy, remove, or reset
| Action | What it does |
|---|---|
| Copy Module Rules | Copies the module's rule onto one command so you can adjust it |
| Remove Override | Deletes a command's own rule so it follows its module again |
| Reset | Removes every rule on that target and returns it to enabled and allowed |
Limits
Each allow or deny list holds up to 25 roles and up to 25 channels or categories. Limits are the same on Public, Prime, and Custom.
Commands
| Command | What it does | Permission |
|---|---|---|
/settings command command:<name> | Open rules for one command | Manage Server |
/settings command module:<name> | Open rules for a whole module | Manage Server |
Use the name shown in /help and the command list, such as purge or economy.
Troubleshooting
A member is denied even though their role is allowed. Check every list and the module rule. A denied user, another denied role, the channel, or its category can still block the command.
The server owner can use a disabled command. This is intended, so owners can't lock themselves out.