Skip to main content
Burger Bot
Burger Bot uses two distinct permission systems that work together: Discord bot permissions (what the bot itself is allowed to do in your server) and Burger Bot user permission tiers (which of your members can run which commands). Understanding both systems is key to a secure, well-functioning setup.

​
Bot Permissions — What Burger Bot Needs

Burger Bot needs certain Discord permissions to carry out actions on your server. The easiest and most reliable approach is to grant the Administrator permission during the invite flow — this covers everything and prevents subtle issues as you enable new modules.
The Administrator permission is strongly recommended for Burger Bot. If your server policy prohibits granting Administrator to bots, use the granular permissions list below — but be aware that missing permissions will cause specific features to fail silently or with an error.

Administrator Permission

Granting Administrator gives Burger Bot full server permissions, ensuring every feature works correctly without any additional configuration. This is the officially recommended setup for all Burger Bot deployments.

​
Granular Permissions (Advanced)

If you prefer to grant only the minimum required permissions, the table below shows what each permission is used for:
Discord PermissionUsed For
Manage MessagesDeleting rule-breaking messages, clearing spam during moderation actions
Kick MembersExecuting kick commands issued through Burger Bot
Ban MembersExecuting ban and unban commands issued through Burger Bot
Manage ChannelsCreating and configuring log channels during /setup
Manage RolesAssigning and removing mute/timeout roles during moderation
Read Message HistoryReviewing message context for moderation and audit logging
Send MessagesPosting responses, embeds, logs, and notifications in channels
Embed LinksSending rich embed messages for logs, session votes, and suggestions
Attach FilesAttaching log exports and report files
Use Application CommandsRunning and responding to slash commands
View ChannelsSeeing and operating within configured channels
Moderate MembersApplying Discord timeouts during mute actions
Even one missing permission can break a specific feature. For example, without Manage Roles, Burger Bot cannot apply mute roles. If you encounter unexpected errors, check that all permissions above are granted to Burger Bot’s role in your server settings.

​
User Permission Tiers — Who Can Run What

Burger Bot has four internal permission levels that determine which commands your members can access. These tiers are independent of Discord’s built-in permission system — a member only needs their Burger Bot role tier to use commands, not Discord-level permissions.

Tier 1 — Server Admin

Full access to all Burger Bot commands and configuration.Members with the configured Server Admin role can:
  • Run /config to change any bot setting
  • Access all moderation, staff, and session commands
  • View and manage audit logs
  • Enable or disable bot modules
  • Manage staff feedback and suggestions pipelines
Assign this tier to your server owners, co-owners, and senior administrators.

Tier 2 — Staff

Access to staff-facing feature commands.Members with the configured Staff role can:
  • Manage ERLC session votes and announcements
  • Review, approve, and deny suggestions
  • Submit and view staff feedback
  • Access staff-tier information commands
Assign this tier to your general staff team — people who manage day-to-day community operations but don’t need to change bot configuration.

Tier 3 — Moderator

Access to moderation commands.Members with the configured Moderator role can:
  • Warn, mute, unmute, kick, and ban members
  • View a member’s infraction history
  • Use message management commands
Assign this tier to your moderation team. They can act on rule violations but cannot access configuration or staff management tools.

Tier 4 — Regular Member

Access to community-facing commands.All members of your server (no special role required) can:
  • Submit suggestions via the suggestions module
  • Vote in ERLC session polls (if enabled)
  • View their own warnings (if the self-lookup command is enabled)
No configuration needed — every member falls into this tier by default.

​
Configuring Role Tiers

You assign Discord roles to each Burger Bot permission tier using the /config roles command. Only members with the Server Admin tier (or a Discord Administrator) can run this command. 
/config roles admin:@YourAdminRole staff:@YourStaffRole moderator:@YourModRole
You can assign multiple Discord roles to the same tier. For example, if you have both a @Head Admin and @Admin role that should both have full access, run /config roles admin:@Head Admin and then /config roles admin:@Admin to add the second role to the same tier.
To review your current role configuration at any time: 
/config roles view
Burger Bot checks permission tiers at command execution time. If you update a member’s roles in Discord, their Burger Bot access level updates immediately — no bot restart or cache reset needed.