Skip to main content
The /permissions command provides an interactive interface to configure role-based access control for admin commands and raid signups.
Requires Manage Server permission or a configured admin role.

​
Command Signature

/permissions

​
Permission Types

RaidBot uses a flexible permission system:
  1. Global Admin Roles - Can use all admin commands
  2. Per-Command Roles - Can use specific admin commands
  3. Signup Roles - Can sign up for raids/museums
  4. Special Permissions - Stats viewing, etc.

​
Always Allowed

These always bypass role checks:
  • Server Owner - Full access to everything
  • Manage Server Permission - Full access to admin commands

​
Interactive Panel

The panel shows:
  • Current global admin roles
  • Selected command and its configured roles
  • Controls to add/remove roles

​
Panel Workflow

  1. Select a command/permission type from dropdown
  2. View currently configured roles
  3. Use role selector to add roles
  4. Click “Clear roles” to remove all

​
Configurable Commands

Roles that can use all admin commands.Grants access to:
  • All commands listed below
  • All admin-only features
Use case: Set “Officer” or “Raid Leader” role here to give full access.

​
Permission Inheritance

Hierarchy:
  1. Server Owner (always allowed)
  2. Manage Server permission (always allowed for admin commands)
  3. Global admin roles
  4. Per-command roles
Example: If user has:
  • “Officer” role (in Global admin)
  • No per-command roles
They can use all admin commands. If user has:
  • “Raid Leader” role (in /create permissions only)
  • No global admin role
They can only use /create.

​
Configuration Examples

​
Example 1: Simple Setup

Global admin roles: @Officer
Raid signup: (empty - everyone)
Museum signup: (empty - everyone)
Result:
  • Officers can use all admin commands
  • Everyone can sign up for raids and museums

​
Example 2: Restricted Signups

Global admin roles: @Officer
Raid signup: @Guild Member
Museum signup: @Guild Member, @Trial Member
Result:
  • Officers can use all admin commands
  • Only Guild Members can sign up for raids
  • Guild Members and Trial Members can sign up for museums

​
Example 3: Delegated Permissions

Global admin roles: @Officer
/create: @Raid Leader
/raid: @Raid Leader
/poll: @Event Coordinator
Raid signup: (empty - everyone)
Result:
  • Officers can use all admin commands
  • Raid Leaders can create and manage raids
  • Event Coordinators can create polls
  • Everyone can sign up

​
Example 4: Stats Access

Global admin roles: @Officer
View others' stats: @Officer, @Recruiter
Result:
  • Officers have full admin access
  • Recruiters can view member stats but not manage raids

​
Using the Panel

/permissions
→ Select "Global admin roles" from dropdown
→ Use role selector to pick @Officer, @Raid Leader
→ Both roles now have full admin access

​
Best Practices

Global Admin:
  • Keep this limited to trusted leadership
  • Use per-command roles for delegation
Signup Restrictions:
  • Only restrict if you have verification/onboarding
  • Consider separate museum permissions (lower barrier)
  • Test with an alt account to verify
Delegated Permissions:
  • Give /create to experienced raiders
  • Keep /raid management more restricted
  • /permissions should stay admin-only
Stats Viewing:
  • Consider allowing officers to view stats
  • Helps with recruitment and activity tracking
  • Doesn’t grant raid management powers

​
Troubleshooting

“Missing Access” error:
  • Check if user has Manage Server permission (bypasses roles)
  • Check if user has global admin role
  • Check if user has the specific command role
  • Verify roles are still valid (not deleted)
Can’t sign up for raids:
  • Check if signup roles are configured
  • Verify user has one of the allowed roles
  • Clear signup roles to allow everyone

Build docs developers (and LLMs) love

Get started for freeTalk to us