Permission Setup Guide¶

This guide explains how to control who can use each command category.

Prerequisites¶

Administrator permission (or Manage Server)

How Permission Overrides Work¶

Armory Bot adds role/user permission overrides on top of Discord permissions.

Check Order¶

When someone runs a command, checks happen in this order:

Manage Server permission — always allowed
User override — explicit allow/deny for that user
Role override — allow/deny inherited from roles
Default — denied

The first match wins.

Command Categories¶

Permissions are set by category, not by individual command.

The slash command parameter is named command_group, but in this guide we refer to it as a command category.

Category Key	Commands Covered
`shop`	`/shop` user economy commands
`economy`	`/economy` admin commands
`moderation`	`/mod`, `/cases`, `/mod-debug`
`admin`	`/server`, `/permissions`
`leveling`	`/levels` admin XP commands
`logging`	`/logging`
`welcome`	`/welcome`
`voice`	`/voice`, `/voice-config`
`timers`	`/timer`, `/event`
`roles`	`/rolemenu` and role-management tooling
`operations`	`/deploy`, `/bounties`, `/operations`, `/bounty`
`tags`	`/tag`, `/trigger`
`polls`	`/poll`
`announcements`	`/announce`
`suggestions`	`/suggestion`

Grant Access¶

Grant to a Role¶

/permissions grant command_group:economy role:@Treasurer reason:"Treasury team access"

Use exactly one target field per command (role or user).

Grant to a User¶

/permissions grant command_group:moderation user:@TrustedHelper reason:"Trial moderator"

View Current Overrides¶

/permissions list
/permissions list command_group:economy
/permissions list user:@TrustedHelper

Revoke Access¶

/permissions revoke command_group:economy role:@Treasurer reason:"No longer needed"
/permissions revoke command_group:moderation user:@TrustedHelper

Use exactly one target field per command (role or user).

Example Setup¶

# Moderators
/permissions grant command_group:moderation role:@Moderator

# Economy team
/permissions grant command_group:economy role:@Treasurer

# Operations team
/permissions grant command_group:operations role:@EventTeam

# Role team
/permissions grant command_group:roles role:@RoleTeam

Update Timing¶

Permission checks are actively invalidated after writes, so changes are typically visible immediately. If you are troubleshooting a stale result across multiple instances, wait up to a few minutes for all caches to settle.

Operations Roles¶

Operations launch/campaign/wager roles are configured separately from /permissions.

Troubleshooting¶

Problem	Solution
"Permission denied" for an admin	Confirm the user has Manage Server and the bot role is high enough
Override not taking effect	Wait a few minutes, then run the command again
Can't grant to a category	Category keys must match `^[a-z0-9._-]{1,50}$` (lowercase, no spaces)