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.

Command permissions belong to the Settings module. Configure one target at a time from Discord or manage the full command catalog from the Dashboard.

Features

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 command access. Discortics needs Send Messages and Embed Links for the Discord settings panel.

Server owners and Discortics owners bypass access rules. Command rules do not grant Discord permissions that a command normally requires. For example, allowing a member to use a moderation command does not give them Discord's Moderate Members permission.

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

Run /settings command target:<name>.
Enter a command name such as purge or a module name such as economy.
Check the panel author line. It identifies the target as command:<name> or module:<name>.
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 that module. A command rule affects only one command.

When both exist, both rules apply. A deny from either rule blocks the command. Editing one command does not silently replace its module restrictions.

Use module rules for broad policy, then add command rules only for exceptions or stricter controls.

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

Open the target with /settings command target:<name>.
Select Users.
Choose users in Allowed or Denied.
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

Open Roles.
Select up to 25 allowed roles and up to 25 denied roles.
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

Open Channels.
Select text channels, announcement channels, or categories in Allowed or Denied.
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 Workflow

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

Command	Purpose	Required user permission
`/settings command target:<name>`	Open access settings for one command or module	Manage Server

The target option is required. Enter the internal command or module name shown in Discortics help and command lists.