Skip to main content
Burger Bot’s audit log system gives you a real-time, structured record of everything happening in your server — from members joining and leaving to messages being deleted and roles being updated. Setting it up takes just a few minutes and gives your moderation team a powerful visibility tool.

​
Before You Begin

Make sure you have:
  • Manage Server permission (or Administrator) in your Discord server
  • Burger Bot already invited and online in your server
  • A plan for which channels you’d like to use for logs (one channel is fine, but multiple categories are supported)

​
Setup Steps

1

Create a Dedicated Audit Log Channel

In your Discord server, create a new text channel for audit logs (e.g., #audit-logs or #server-logs).Recommended settings:
  • Set channel permissions so only admins and moderators can view it
  • Disable @everyone read access
  • Optionally create a logs category and add multiple channels for different event types (e.g., #member-logs, #message-logs)
Using separate channels per log category keeps your audit logs readable and prevents a single busy event type (like message deletes) from drowning out everything else.
2

Run /config channels

Open any channel where Burger Bot has access and run:
/config channels
This opens Burger Bot’s interactive channel configuration panel. Locate the Audit Log Channel field and select the channel you created in Step 1. Save your changes.
3

Configure Event Types (Optional)

By default, Burger Bot logs all supported event types. To customize which events are logged, run:
/config
Navigate to Audit Logs → Event Settings and toggle individual event categories on or off. You can enable or disable:
  • Member Events (joins, leaves, bans, role changes)
  • Message Events (deletes, edits, bulk deletes)
  • Channel Events (create, delete, update)
  • Role Events (role create, delete, update)
  • Voice Events (join, leave, move)
Changes to event settings take effect immediately — no restart or re-invite required.
4

Test Your Configuration

Once configured, trigger a test event to confirm logs are flowing correctly. The easiest way is to:
  1. Have a member join or leave your server, or
  2. Delete a test message in any channel
You should see a formatted embed appear in your audit log channel within a few seconds.
If no log appears, double-check that Burger Bot has View Channel, Send Messages, and Embed Links permissions in your audit log channel.

​
Required Bot Permissions

For audit logs to function correctly, Burger Bot requires the following Discord permissions:
PermissionWhy It’s Needed
View Audit LogRequired to capture ban/unban and moderator action details
Send MessagesTo post log embeds to the log channel
Embed LinksTo format log entries as rich embeds
Read Message HistoryFor bulk delete logging
If you manage a large or active server, consider giving Burger Bot a dedicated role with exactly the permissions it needs rather than granting Administrator. This follows the principle of least privilege and is a best practice for any bot.