Guide/Protect your server/Logging

Discord Logging Bot: Deleted Messages, Joins & Audit Logs

Seventeen log categories to channels, message forensics, retention, search and export, invite tracking.

Quick answer

Route and search

!logs channel #logs
!logs channel #message-logs message
!logs route #staff-chat #staff-logs        # everything from one source channel to its own log
!logs messages on attachments:true
!logs retention 60
!logs search user:@x event:message.delete after:2026-09-01
!logs export csv user:@x

Ask the guide

Step by step

Dashboard: Security → Logging lists all seventeen categories with a channel picker and an on/off switch each, plus a default channel and a one-click "send every category here". The commands below do the same from Discord.

Fifteen log categories: message, member, voice, moderation, role, channel, server, webhook, emoji, security, config, invite, thread, poll, stage. Each category can go to its own channel or to the default channel, be toggled, ignore channels and roles, and use a custom embed as its format.

!logs channel #logs                          default channel for everything
!logs channel #message-logs message         one category to its own channel
!logs toggle voice off
!logs ignore message #bot-spam · !logs ignore member @Bots
!logs format moderation modlog-card         custom embed as the format
!logs messages on attachments:true          store content for edit/delete forensics
!logs retention 30                           days (1–90; premium up to 365)
!logs status

Searching and exporting

!logs search user:@x event:message.delete channel:#general after:2026-09-01 severity:high
!logs history 123456789012345678             edit history of one message
!logs export csv user:@x

Filters: user:, event: (e.g. message.delete, member.join, voice.move, role.update), channel:, after:/before:, severity:, case:. The dashboard has the same search under Security → Logs with decrypted message content for staff who hold logs.deleted.

Invites

Join attribution needs Manage Server so the bot can read invite uses; without it joins show as "inferred". !invited [@user] lists the actual people someone invited, newest first, with who is still here, who left and rejoins. !invites [@user] (alias !i) shows joins, still here, left, fake (left within minutes), rejoins and members who never finished onboarding. Resets: !ri for yourself, !ri @user and !ri all with Manage Server.

Copy and try

Route and search

!logs channel #logs
!logs channel #message-logs message
!logs route #staff-chat #staff-logs        # everything from one source channel to its own log
!logs messages on attachments:true
!logs retention 60
!logs search user:@x event:message.delete after:2026-09-01
!logs export csv user:@x

Good to know

A purge (bulk delete) log comes with a text file of the deleted messages when message storage is on (!logs messages on).
If logs stop arriving, run !logs status: the Delivery line says why, for example a missing permission or a deleted log channel. Failed sends are retried, and one bad log never blocks the others.
Reaction add/remove events are only stored when logs.storeReactions is on (off by default; they are high-volume). Ignored channels are honoured.
Message content is only stored when !logs messages is on, and is encrypted at rest.
Retention is capped by the plan (90 days free, 365 premium).

If it does not work

Nothing arrives in the log channel. The bot lacks View Channel / Send Messages / Embed Links there, or the category is off (!logs status).

Still stuck? Ask in the support server.