← All articles

How to Read the Discord Audit Log (and Keep Mods Accountable)

Published 18 Nov 2026

Also available in: Deutsch · Français · Português · Español

Someone deleted the #announcements channel. A long-time member says they were banned for no reason. Half your roles suddenly have the Mention @everyone permission. In all three cases the first place to look is the same: the audit log. It's Discord's built-in record of administrative actions, and once you know how to read it, it becomes the backbone of a trustworthy moderation team.

Where to find it

Open Server Settings and choose Audit Log. You'll only see it if you have the View Audit Log permission, which is a good permission to give every moderator and nobody else. Members without it don't know the log exists, and that's fine.

Anatomy of an entry

Each entry answers four questions:

  • Who performed the action (a person or a bot).
  • What they did: banned a member, updated a role, created a channel.
  • To what: the member, role, channel or setting affected.
  • When, plus the reason if one was given.

Click an entry to expand it. For updates, Discord shows the before-and-after values, which is how you discover that a role's colour changed or that a specific permission was switched on.

Filtering to find what you need

A busy server produces hundreds of entries a week. Two filters at the top of the log save you from scrolling:

  1. Filter by user to see everything one moderator or bot did.
  2. Filter by action to see, for example, only bans or only channel deletions.

Combining them answers questions like "which roles did this admin edit yesterday?" in seconds.

What the audit log records, and what it doesn't

Recorded Not recorded
Bans, unbans, kicks and timeouts Content of deleted messages
Role creation, edits and assignments Members deleting their own messages
Channel creation, edits, deletions and permission overwrites Message edits
Invites, webhooks, emojis and stickers Ordinary members joining or leaving
Messages deleted by someone other than the author (grouped) Voice activity, except moves and disconnects by moderators
Server setting changes, bots added, AutoMod actions Anything older than Discord's retention window

The right column is why most servers also run a logging bot. The audit log tells you that a moderator deleted three messages from a member; it doesn't tell you what those messages said.

The retention limit

Discord keeps audit log entries for 45 days. After that they're gone. If a dispute comes up about something from three months ago, the native log can't help you. That's another reason to keep your own durable record of sanctions, ideally one where every case has a number, a reason and a moderator attached.

Bots in the audit log

When a bot bans someone, the audit log shows the bot as the actor, not the moderator who typed the command. Well-built bots put useful context in the reason field, but the reliable answer to "who really did this?" lives in the bot's own case history. Keep that in mind before accusing anyone based on the native log alone.

A simple accountability routine

An audit log only helps if someone actually reads it. A light routine for a team of any size:

  • Reasons are mandatory. Make it a staff rule: no ban, kick or timeout without a reason. "Spam" isn't enough; say what happened.
  • Weekly skim. One senior moderator spends ten minutes a week filtering by bans, role updates and channel deletions. Anything surprising gets a polite question, not an accusation.
  • Watch for unusual bursts. Many bans or role changes in a few minutes from one account can mean a compromised account or a moderator acting out. Check immediately.
  • Least privilege. Don't hand out Administrator. Give moderators exactly the permissions they need, so the log shows a smaller and more meaningful set of actions.
  • Require 2FA for moderators. Discord lets you require two-factor authentication for members with moderation permissions, which makes stolen-account incidents much rarer.

Where MagnificBot fits

MagnificBot complements the audit log on both of its weak points. Its moderation module stores every sanction as a numbered case with the moderator, reason and time, and when a moderator bans, kicks or times someone out directly through Discord's menus, that action is recorded as a case as well. Your history stays complete no matter how the action was taken, and it doesn't vanish after 45 days.

The logging module covers what the audit log leaves out, such as message, member and voice events, in channels you choose. And because the dashboard has its own audit trail, changes made in the panel by your staff are traceable too. Combine that with panel roles (Admin, Moderator, Support, Designer, Reader) and you can give people exactly the access they need without extra Discord permissions. All of it is included in the free plan.

FAQ

Who can see the Discord audit log?

Only members with the View Audit Log permission, which Administrator includes. Regular members can't see it.

How long does Discord keep audit log entries?

45 days. Keep your own case history if you need older records.

Can I see what a deleted message said in the audit log?

No. The audit log records that a moderator deleted messages, not their content. A message logging setup is needed for that.

Why does the audit log show a bot instead of the moderator?

Because the bot performed the action. Check the reason field or the bot's case history to see which moderator issued it.

Want a moderation history that outlasts the audit log? Log in at app.magnificbot.com and turn on the moderation and logging modules.

Teste MagnificBot kostenlos

Alle Module inklusive, eingerichtet über ein Web-Dashboard. Ohne Kreditkarte, ohne Zeitlimit.

Zu Discord hinzufügen – kostenlos