Dispatch.IO Logo
Server setup

Logs

Browse your server's Discord audit log and the history of changes made on the dashboard, with filters, details and export.

Updated on October 15, 2026#journaux

Search the documentation

Type a keyword: a command, a module, a dashboard page…

The Administration group of the menu has two history pages:

Menu pageWhat it showsSource
Discord Audit LogsActions taken on Discord: bans, kicks, channels and roles created or edited, deleted messages, AutoMod…Discord's audit log, read by the bot.
Configuration LogsChanges made on the dashboard: who changed which setting, and when.The Dispatch.IO website history.

These pages are read-only. They're for server owners and administrators. For the log messages the bot posts in your Discord channels, see Logs (module).

Discord Audit Logs: the page

In the left menu, Administration group, click Discord Audit Logs.

Discord Audit Logs page with several events
The Discord Audit Logs page.
  1. The buttons: Auto (15s) / Auto Off (automatic refresh every 15 seconds, on by default), Refresh, Export CSV and Export JSON.
  2. The counters: Total Events, Activity This Month, Moderation & Sanctions and Channels & Roles.
  3. The filters (see below).
  4. The table: Date & Time, Action (with its category), Author / Moderator, Target, Reason / Note, level and Inspect. 25 rows per page.
FilterValues
Filter by monthAll months or a specific month.
CategoryAll categories, Moderation & Sanctions, Role Management, Channel Management, Messages & Purge, Server Configuration, AutoMod & Security, Integrations & Webhooks, Other events.
Severity levelAll levels, INFO, WARN, CRITICAL.
SearchLooks in the action, author, target, reason and changes ("Search by action, author, target, reason, or ID...").

Reset filters clears everything. Examples of actions per category and level (action labels are shown in French, see below):

CategoryExample actionsLevel
Moderation & SanctionsMember banned ("Bannissement d'un membre")CRITICAL
Member kicked, member edited (timeout / nickname), member disconnected from voiceWARN
Member unbanned, members moved in voiceINFO
Channel ManagementChannel deleted ("Suppression de salon")CRITICAL
Channel created or edited, channel permissions, threadsINFO / WARN
Role ManagementRole deleted ("Suppression de rôle")CRITICAL
Role created or edited, member roles updatedINFO
Messages & PurgeBulk message purge ("Purge de messages en masse")CRITICAL
Message deleted, message pinnedWARN / INFO
AutoMod & SecurityMessage blocked by AutoMod, member timed out by AutoModCRITICAL
Server ConfigurationServer update, emojis, stickers, invitesINFO
Integrations & WebhooksBot added, webhook createdINFO

Event details

Click Inspect at the end of a row to open the event sheet:

  • Action Author and Affected Target (with their avatar and ID);
  • Provided Reason, if the author gave one;
  • Detected Changes (Diff): a Property / Before / After table (for example a channel's old and new name);
  • Metadata & Raw JSON, with Copy JSON.
Audit log event sheet with its changes
An event's details: author, target and changes.

Good to know about the audit log

  • The page reads the last 100 events of Discord's audit log; filters and pagination apply to those.
  • The bot needs the View Audit Log permission. Without it, the list stays empty, with no error message.
  • Actions taken by Dispatch.IO (raid mode kicks, anti-raid sanctions, moderation commands…) appear with Dispatch.IO as the author.
  • Warnings (/warn) and the infraction history recorded by the bot don't show up here: check them with /infractions (see Moderation).
  • Action labels, month names and a few messages (export, errors) are shown in French, whatever the site language.
  • Data is cached for 30 seconds: a brand-new event can take up to 30 seconds to appear.
  • Export CSV / Export JSON download the page currently shown (25 rows max), with the current filters.

Configuration Logs: the page

In the left menu, Administration group, click Configuration Logs.

Configuration Logs page with several changes
The Configuration Logs page.
  1. The same buttons as the audit log: Auto (15s), Refresh, Export CSV, Export JSON.
  2. The counters: Total Configurations, General Settings, Welcome & Channels, Emergency & Roles.
  3. The filters: Filter by month, Category (a module: Security, Word reaction, RSS feeds…), Severity level (INFO, WARN, CRITICAL) and search by action, author, parameter or ID.
  4. The table: Date & Time, Action / Module, Author (Moderator), Modified Settings and Inspect.

What gets recorded

Every save made on a page of your server's dashboard adds a row, with its author. A few examples (labels are shown in French; the English meaning is given here):

ActionCategoryLevel
Raid mode update ("Mise à jour du mode raid")SecurityCRITICAL
Anti-raid update, whitelist updateSecurityWARN
Emergency & alerts module configurationEmergency & AlertsWARN
General settings updateGeneral SettingsINFO
Server channel assignmentChannels & LayoutINFO
Word reaction, temporary channel, RSS feed, social network… created / updated / deletedThe module concernedINFO (WARN for a deletion)
Other commands updateOther commandsINFO

The Inspect button opens the sheet: Action Author, Server & Context, Applied Changes (Diff) with Property / Before / After, then the raw JSON. When a save didn't change any specific field, the sheet says "No specific field change detected (global configuration saved).".

Configuration change sheet with the before / after diff
A change's details: who, what, before and after.

Note

Only changes made on the website are listed here. Settings changed on Discord with /config don't appear: the bot records them in the General Server Logs channel. XP edits made in Members & XP aren't recorded either.

Refreshing

  • Both pages refresh every 15 seconds while Auto (15s) is on; click it to switch to Auto Off, then use Refresh whenever you want.
  • Data is cached for 30 seconds on the server.
  • If something goes wrong, the message "Impossible d'actualiser les logs du serveur." (or "… les logs de configuration.", meaning the logs couldn't be refreshed) appears: try again a bit later.

Updated on October 15, 2026