Skip to main content

​
Command Permissions

Control exactly who can use each slash command in your Discord server. Technified’s command permission system gives you granular control over command access, from allowing everyone to restricting to specific roles.

​
What are Command Permissions?

Command permissions let you restrict or allow access to Technified’s slash commands based on user roles. This is separate from Discord’s native permission system and gives you more flexibility in managing bot access.

​
Available Commands

Technified includes these configurable commands:

/verify

Link a Roblox account to Discord

/unlink

Remove Roblox account link

/reverify

Update verification status

/sync

Manually update your roles

/force_sync

Force-sync a specific user (Admin)

/lookup

Check linked accounts

/config

View server configuration

/binding

Manage role bindings

​
Permission Modes

Each command can be configured with one of four permission modes:

​
Everyone

Who can use it: All server members The command is available to everyone in your server, regardless of their roles or permissions. This is the most permissive setting.
Best for: Commands like /verify, /sync, /reverify that regular members need access to for basic functionality.

​
Administrators Only

Who can use it: Users with Discord’s “Administrator” permission Only users who have the Administrator permission in your Discord server can use this command. This is Discord’s built-in permission.
Best for: Sensitive commands like /config, /binding, /force_sync that should only be accessible to server administrators.

​
Specific Roles

Who can use it: Users with any of the selected roles The command is only available to users who have at least one of the roles you specify. You can select multiple roles. Example:
  • You have roles: @Moderator, @Helper, @Admin
  • You configure /lookup to require @Moderator OR @Admin
  • Users with either role can use the command
Best for: Commands like /lookup or /force_sync where you want multiple specific roles to have access.

​
Role or Higher

Who can use it: Users with the selected role OR any role higher in the hierarchy The command requires a specific role, but also allows users with roles positioned higher in Discord’s role hierarchy to use it. How Discord Role Hierarchy Works:
  • Roles higher in your server’s role list = higher in hierarchy
  • Higher roles have more “power” than lower roles
  • Drag roles up/down in Server Settings → Roles to reorder
Example:
  • Role hierarchy (top to bottom): @Owner, @Admin, @Moderator, @Member
  • You configure /lookup to require @Moderator or higher
  • Users with @Owner, @Admin, or @Moderator can use the command
  • Users with only @Member cannot use the command
Best for: Commands where you want a cascading permission system, allowing senior staff to automatically have access to junior staff commands.

​
Configuring Command Permissions

1

Open Server Settings

Navigate to the Technified Dashboard, select your server, and go to Server Settings → ** Command Permissions**
2

Select a Command

Find the command you want to configure from the list
3

Choose Permission Mode

Select one of the four modes from the dropdown:
  • Everyone
  • Administrators Only
  • Specific Roles
  • Role or Higher
4

Configure Roles (if applicable)

If you selected “Specific Roles” or “Role or Higher”, choose which roles should have access
5

Save Changes

Click Save Permissions at the bottom of the page

​
Common Configurations

Here are recommended permission setups for different server types:

​
Public Community Server

  • /verify → Everyone
  • /sync → Everyone
  • /reverify → Everyone
  • /unlink → Everyone

​
Permission Hierarchy Explained

Understanding how role hierarchy works is key to using “Role or Higher” effectively.

​
Example Hierarchy

┌──────────────┐
│   @Owner     │ ← Highest (can use everything)
├──────────────┤
│   @Admin     │
├──────────────┤
│  @Moderator  │
├──────────────┤
│   @Helper    │
├──────────────┤
│   @Member    │ ← Lowest
└──────────────┘
If you set a command to require @Helper or higher:
  • ✅ @Owner → Can use
  • ✅ @Admin → Can use
  • ✅ @Moderator → Can use
  • ✅ @Helper → Can use
  • ❌ @Member → Cannot use
The role hierarchy is determined by the position of roles in your Discord server’s role list, NOT by their names or colors.

​
Best Practices

Always allow everyone to use /verify, /sync, and /reverify. These are essential for members to link and maintain their accounts.
Keep /config, /binding, and /force_sync restricted to administrators only. These commands can modify server settings and should not be accessible to regular members.
If you have multiple staff levels (Helper, Moderator, Admin), use “Role or Higher” to automatically grant permissions as staff get promoted.
Keep a note of which roles can use which commands. This helps when onboarding new staff or troubleshooting access issues.
After changing permissions, test with an alt account or ask a team member to verify the changes work as expected.
As your server grows and roles change, review command permissions quarterly to ensure they still match your needs.

​
Troubleshooting

Possible causes:
  • User doesn’t have the required role
  • Permission mode is set too restrictively
  • Discord’s slash command cache needs to refresh (have user restart Discord)
Solution:
  • Check the command’s permission mode in settings
  • Verify the user has the correct role
  • Ask user to restart Discord to refresh command cache
Possible causes:
  • Roles are not in the correct order in Discord
  • Technified’s role is not high enough in the hierarchy
Solution:
  • Go to Server Settings → Roles in Discord
  • Drag Technified’s role above all roles you want it to manage
  • Reorder roles to match your desired hierarchy
Possible causes:
  • User doesn’t actually have Administrator permission
  • They have a role named “Admin” but not the Administrator permission
Solution:
  • Check the user’s actual permissions in Discord
  • Verify their role has the “Administrator” permission checkbox enabled
  • Alternatively, use “Specific Roles” mode and add their role
Solution:
  • Click “Save Permissions” after making changes
  • Wait 10-30 seconds for changes to propagate
  • Have users restart Discord to refresh command cache

​
Next Steps

Commands Reference

See full list of all commands and their parameters

Role Bindings

Learn about automatic role assignment

Staff Management

Configure staff permissions and access

Best Practices

Security and organization tips
Command permissions give you fine-grained control over bot access. Configure them once, and they’ll automatically enforce your server’s access policies.