Command Permissions Guide

The Command Permissions system controls who can run Discortics commands and where they can run them. Rules can target one command or every command in a module.

Use Command Permissions when a command should be staff-only, limited to #bot-commands, blocked for one role, or disabled across the server.

Set up a staff-only command

This example allows only the Moderator role to use /purge.

What you can control

• Enable or disable a command across the server.
• Enable or disable every command in a module.
• Allow or deny specific users.
• Allow or deny up to 25 roles per list.
• Allow or deny up to 25 channels or categories per list.
• Start with everyone allowed or everyone denied in each scope.
• Copy a module rule into a command-specific rule.
• Remove a command override so it follows its module rule again.

Before you begin

• You need Manage Server to edit access.
• Discortics needs Send Messages and Embed Links for the Discord panel.
• Server owners and Discortics owners bypass access rules.
• Allowing a command never grants the Discord permission it normally requires.

Important: Restricting a command does not remove it from Discord's slash-command picker. A blocked member may still see the command, but Discortics denies it when they try to run it.

Open an Access Panel

1. Run /settings command command:<name> for one command, or /settings command module:<name> for a complete module.
2. Enter a command name such as purge or a module name such as economy.
3. Check the panel author line. It identifies the target as command:<name> or module:<name>.
4. Use the status, Channels, Roles, or Users controls.

Changes save immediately in Discord.

Command Rules and Module Rules

• A module rule affects every command in its module.
• A command rule affects one command only.
• When both exist, both apply; a deny from either blocks the command.
• Editing a command does not replace its module restrictions.
• Use module rules for broad policy and command rules for exceptions.

Example:

• Disable the Economy module for the server.
• Add an explicit user or role allow for staff who may still use Economy.
• Add a command-specific deny for one sensitive Economy command.

Server Status

The first button enables or disables the target server-wide.

• Enabled: Scope rules decide access normally.
• Disabled: Access is blocked unless a user, role, channel, or category has an explicit allow and no scope denies the request.

If you want a strict allowlist, set the relevant scope's default to Denied and add the exceptions to its Allowed list.

Scope Rules

Each target can have separate rules for Users, Roles, Channels, and Categories.

Default Allowed

Members pass that scope unless they match its Denied list. Entries in Allowed are explicit exceptions that can permit a server-disabled target, but they still cannot override a deny in another scope.

Use this for a command that should work almost everywhere except selected users, roles, or places.

Default Denied

Members fail that scope unless they match its Allowed list.

Use this for staff-only commands, commands limited to a bot channel, or commands enabled only in one server section.

Deny Wins

Within one scope, Denied wins over Allowed. A member with one allowed role and one denied role is denied.

Across all scopes, any deny blocks the command. An allowed user can still be blocked by a denied role, channel, or category.

Restrict by User

1. Open the target with /settings command command:<name>.
2. Select Users.
3. Choose users in Allowed or Denied.
4. Set the default to Allowed or Denied.

User rules are useful for temporary exceptions. Prefer role rules for groups that change often.

Restrict by Role

1. Open Roles.
2. Select up to 25 allowed roles and up to 25 denied roles.
3. Set the default behavior.

For a staff-only command, set Roles to Default Denied, then add staff roles to Allowed. Remember that a member holding any denied role is blocked even if another role is allowed.

Restrict by Channel or Category

1. Open Channels.
2. Select text channels, announcement channels, or categories in Allowed or Denied.
3. Set the default behavior.

Channels and categories are stored separately but edited in the same panel. A command can be denied by either its channel or its parent category.

Threads follow their parent channel and category rules when Discortics can resolve them.

Example: set Channels to Default Denied, then add #bot-commands and the Community Bots category to Allowed.

Copy Module Rules

When a command belongs to a module with a configured rule, its panel shows Copy Module Rules. This creates a command-specific copy of the current module rule.

The copy does not stay linked. Later module changes still apply as module rules, but they do not rewrite the command copy.

Use this when a command should begin with module policy, then receive its own adjustments.

Remove an Override

Select Remove Override on a command to delete its command-specific rule. The command then follows its module rule and normal required permissions.

This is usually better than manually changing every command scope back to default.

Reset a Rule

Select Reset, then confirm Yes, Reset. This removes every access setting for that target and returns it to the normal default: enabled and allowed.

Warning: Reset removes all user, role, channel, and category lists for the selected command or module. It cannot be undone.

Resetting a command does not reset its module. Resetting a module does not delete command-specific rules.

Dashboard setup

Open Dashboard → Commands to browse modules and their commands. Each target has the same enabled state and user, role, channel, and category access scopes.

The Dashboard is better for comparing several targets. Use the save bar after editing. Discard restores the last saved rules.

Only targets with non-default settings are stored. Returning a target to enabled, default-allowed, and empty lists removes its custom configuration when saved.

Command Reference

Choose either command or module. Enter the internal name shown in Discortics help and command lists.

Frequently Asked Questions

Why is a member denied even though their role is allowed?

Check every scope and both applicable rules. A denied user, another denied role, the current channel, its category, or the module rule can still block the command.

Why can the server owner still use a disabled command?

Server owners bypass command access rules so they cannot lock themselves out of server configuration.

Why does the command still appear in Discord?

Discortics checks access when the command runs. These rules do not change Discord's registered slash-command menu.

Does allowing a command grant its required Discord permission?

No. The member must still have permissions required by that command.

Should I reset or remove an override?

Use Remove Override when one command should return to its module policy. Use Reset when you want to clear the selected target's complete rule.

Are there different limits for Public, Prime, and Custom bots?

No tier-specific command-permission limits are configured. Discord component menus limit each allow or deny list to 25 selections.