Skip to main content
Fire provides granular control over who can use commands and where they can be used. This guide covers all permission-related configuration options.

​
Permission levels

Fire recognizes several permission levels:

Administrator

Users with the Administrator permission or server owner

Moderator

Users with roles designated as moderators via /moderators add

Manage Server

Users with the Manage Server permission

Regular Users

All other server members

​
Setting up moderators

Designate which roles should have moderator permissions for Fire:
1

Add moderator roles

/moderators add <role>
This grants the role access to all moderation commands like /ban, /kick, /mute, etc.
2

View current moderators

/moderators list
Displays all roles configured as moderators.
3

Remove moderator roles

/moderators remove <role>
Revokes moderator permissions from the specified role.
Moderator roles automatically have access to moderator-only commands, but still need appropriate Discord permissions (like Ban Members) to execute actions.

​
Channel restrictions

Restrict Fire commands to specific channels or categories to keep your server organized.

​
Restricting to moderators only

Make specific channels or categories moderator-only for Fire commands: 
/restrict moderator [category]
Behavior:
  • Without [category]: Restricts the current channel to moderators
  • With [category]: Restricts all channels in the category to moderators
Example use cases:
  • Staff channels where only moderators should use bot commands
  • Moderation log channels
  • Private admin channels
To remove the restriction, run the same command again.
Channel-level restrictions are overridden by category-level restrictions. If a category is restricted, individual channel restrictions within it are ignored.

​
Restricting to administrators only

Make specific channels or categories admin-only for Fire commands: 
/restrict admin [category]
Behavior:
  • Without [category]: Restricts the current channel to administrators
  • With [category]: Restricts all channels in the category to administrators
Example use cases:
  • Server configuration channels
  • Owner/admin-only channels
  • Sensitive bot management areas
To remove the restriction, run the same command again.
Administrator restrictions are stricter than moderator restrictions. Users need the Administrator permission or be the server owner.

​
Command-specific permissions

Many commands have built-in permission requirements:
Commands like /ban, /kick, /mute require:
  • User has a moderator role (set via /moderators add), OR
  • User has the corresponding Discord permission (Ban Members, Kick Members, etc.)
Examples:
  • /ban - Requires Ban Members permission or moderator role
  • /kick - Requires Kick Members permission or moderator role
  • /mute - Requires moderator role
  • /lockdown - Requires Manage Channels permission or moderator role
Most configuration commands require Manage Server permission:
  • /logging toggle
  • /logging configure
  • /linkfilter toggle
  • /linkfilter exclude
  • /language (for server-wide changes)
  • /autorole
  • /blacklist
  • /moderators add/remove
This ensures only trusted users can modify server settings.
Some commands require Administrator permission:
  • /restrict admin
These commands have significant impact on server functionality.
Commands available to all users:
  • /help
  • /userinfo
  • /avatar
  • /serverinfo
  • Utility commands
These commands are safe for general use.

​
Permission hierarchy

Fire follows this permission hierarchy (highest to lowest): 
1. Server Owner
2. Administrator permission
3. Manage Server permission
4. Moderator roles
5. Command-specific Discord permissions
6. Regular users
Channel and category restrictions apply after checking user permissions. Even moderators cannot use commands in admin-restricted channels unless they’re also administrators.

​
Best practices

Separate moderator tiers

Create different moderator roles for different trust levels:
  • Trial moderators (limited commands)
  • Full moderators (all mod commands)
  • Senior moderators (config access)

Restrict configuration channels

Use /restrict admin on channels where you configure Fire to prevent accidental changes.

Test restrictions

After setting up restrictions, test with an alt account to verify they work as expected.

Document your setup

Keep a record of which channels are restricted and which roles have moderator permissions.

​
Examples

​
Example 1: Basic moderator setup

1

Create moderator role

Create a role called “Moderator” in Server Settings > Roles
2

Add to Fire

/moderators add @Moderator
3

Grant Discord permissions

Give the Moderator role these Discord permissions:
  • Manage Messages
  • Kick Members
  • Ban Members
  • Manage Nicknames

​
Example 2: Staff channel restrictions

1

Create staff category

Create a category called “Staff” for all staff channels
2

Restrict to moderators

In any channel within the staff category:
/restrict moderator <Staff Category>
3

Verify

Regular users can no longer use Fire commands in any staff channel

​
Example 3: Admin configuration channel

1

Create admin channel

Create a channel called #bot-config
2

Restrict to admins

/restrict admin
3

Configure Fire

Use this channel to safely configure Fire without interference

​
Troubleshooting

Possible causes:
  1. Role not added via /moderators add
  2. Channel is admin-restricted
  3. User lacks required Discord permissions
  4. Fire’s role is lower than the moderator role
Solution: Verify moderator setup and check channel restrictions.
Cause: The channel might be covered by a category-level restriction.Solution: Remove the category restriction first, then manage individual channels.
Cause: No channel restrictions are set.Solution: Use /restrict moderator or /restrict admin to control where commands can be used.
Possible causes:
  1. @everyone role has Discord permissions (Ban Members, etc.)
  2. Channel restrictions aren’t set
  3. Users have Manage Server or Administrator permission
Solution: Review Discord role permissions and consider using channel restrictions.

Server setup

Initial server configuration

Auto-moderation

Automated moderation features

Build docs developers (and LLMs) love

Get started for freeTalk to us