Skip to main content
Burger Bot
Getting Burger Bot fully configured in your server takes just a few minutes. This guide walks you through every step — from the initial invite to verifying that your setup is working correctly. By the end, your server will have moderation, logging, staff roles, and all core modules ready to go.
To complete this setup, you need the Administrator permission in your Discord server (or be the server owner). Burger Bot also requires the Administrator permission to function correctly. See the Permissions Guide for more details.

​
Complete Server Setup

1

Invite Burger Bot to Your Server

If you haven’t already, add Burger Bot to your server using the official invite link. Click the card below or visit the Invite page for step-by-step instructions.

Invite Burger Bot

Open the Discord authorization page to add Burger Bot.
When prompted by Discord, select your server from the dropdown, review the requested permissions, and click Authorize. Grant the Administrator permission when asked for the smoothest experience.
2

Run /setup — Launch the Interactive Wizard

Once Burger Bot appears in your server’s member list, head to any channel where you have permission to send messages and run:
/setup
This launches Burger Bot’s interactive setup wizard. The wizard will ask you a series of questions to configure your server’s core settings — walking you through each section one at a time. You don’t need to know everything upfront; every setting can be changed later with /config.
Run /setup in a private admin channel so the setup prompts don’t clutter your public channels. Burger Bot will only post setup messages in the channel where you run the command.
3

Configure Staff and Moderation Roles

After the initial wizard, use /config roles to assign which Discord roles map to each Burger Bot permission level. You’ll define:
  • Server Admin Role — Full access to all Burger Bot commands and configuration.
  • Staff Role — Access to staff-facing commands like session management, suggestions review, and feedback tools.
  • Moderator Role — Access to moderation commands (warn, mute, kick, ban) without full admin access.
Example:
/config roles admin:@ServerAdmin staff:@Staff moderator:@Moderator
Roles in Burger Bot are separate from Discord’s built-in permission system. A user needs the Discord Administrator permission to run /config, but day-to-day moderation commands are gated by Burger Bot role tiers — not Discord permissions. This lets you give staff members exactly the right level of access without over-granting Discord-level permissions.
4

Configure Log and Feature Channels

Burger Bot posts rich log embeds and feature outputs to dedicated channels. Use /config channels to set these up:
  • Audit Log Channel — All moderation actions, configuration changes, and bot events are posted here.
  • Suggestion Channel — Where member suggestions are posted for staff review.
  • Session Announcements Channel — Where ERLC session votes and announcements are broadcast.
  • Staff Feedback Channel — Where submitted staff feedback is posted for leadership review.
Example:
/config channels auditlog:#audit-logs suggestions:#suggestions sessions:#session-announcements
Create dedicated channels for each of these before running /config channels. Keeping logs and feature outputs in their own channels makes moderation and management much cleaner.
5

Enable Modules

Burger Bot’s features are organized into toggleable modules. After setting up roles and channels, enable the modules your server will use:
/config modules enable:moderation
/config modules enable:suggestions
/config modules enable:sessions
/config modules enable:feedback
/config modules enable:auditlogs
You can enable or disable individual modules at any time without affecting your other settings.
6

Test With a Simple Command

With setup complete, verify everything is working by running a quick test command. A good first test is a moderation action on a test account or bot account in your server:
/warn user:@TestUser reason:Setup test — ignore
Check your audit log channel to confirm the action was logged with a rich embed. If the log appears, your setup is working correctly.
If no log appears, double-check that the Audit Log Channel is set correctly with /config channels and that Burger Bot has permission to send messages in that channel.

​
After Setup — What’s Next?

Permissions Guide

Deep-dive into bot permissions and user permission tiers to fine-tune access control.

Commands Overview

Explore every slash command available in Burger Bot across all modules.

Moderation

Learn how to use Burger Bot’s full moderation suite effectively.

FAQ

Common setup questions and troubleshooting answers.
If Burger Bot is missing the Administrator permission, some commands may fail or produce unexpected behavior. If you chose to grant granular permissions instead, refer to the Permissions Guide to ensure every required permission is checked.