How do you check Discord moderation logs?
6
Configuration steps
5
Final tests
4
Errors solved
~7 min
Reading time
The answer
The short answer
You check moderation logs on Discord in two places. The native audit log (Server settings → Audit log) shows changes made by administrators and bots, but it keeps entries for only 45 days and contains no message content. A bot with its own logging system records far more — in Venon Security, twelve categories including Moderation, Deleted messages, Roles, Invites and Voice — and you route each of them to its own channel in Panel → Moderation → the Logs tab. The Automatic setup button creates the full set of channels and sets the permissions right away.
The content is checked against the bot's configuration — last verified: 2026-08-06.
Context
What the problem is
Without logs, every disputed decision rests on memory and screenshots. During an appeal against a penalty there is no way to establish who issued it and why, and after an incident the sequence of events is missing. Discord's audit log alone is not enough, because it does not record the content of deleted messages and disappears after 45 days.
Without an extra bot
What you can do with Discord alone
- 01
Open Server settings → Audit log and filter the entries by member or action type.
- 02
Remember that the audit log keeps entries for 45 days and contains no message content.
- 03
Create a separate channel category for logs, visible only to the staff.
- 04
Agree on a rule that every penalty carries a reason — without it a log is just a list of names.
Venon Security
What Venon Security adds
Twelve log categories can be routed to separate channels, so penalty logs do not drown in the stream of joins and leaves.
The Automatic setup button creates the full set of channels and sets their permissions in one step.
The log access role limits who can read the audit trail, and the /retention command lets you control how long the data is kept.
Configuration
Configuration step by step
0 of 6 steps
Work out what you are looking for
Before you start browsing channels, establish the type of event. One place covers penalties, another deleted messages, and another permission changes.
- A penalty issued by a moderator → the Moderation category.
- A message that vanished → the Deleted messages category.
- A change to a member's roles → the Roles category.
- Who invited a given person → the Invites and Deleted invites categories.
- A change to server or channel settings → the Server and Channel edits categories, and for panel configuration changes: Panel → Server → Change log.
Enable the log categories
Panel → Moderation → the Logs tabClick Automatic setup if you are starting from nothing — Venon creates the channels and assigns them to the categories. Changes save immediately, both the switch and the channel choice.
- The minimum for moderation: Moderation, Deleted messages, Roles.
- For protection: Invites, Deleted invites, Server.
- Route high-traffic categories such as Voice or Reactions to their own channels — otherwise they swamp the penalty channel.
Limit access to the logs
Panel → Moderation → the Logs tab → Log access role (ID)Logs contain the content of deleted messages and the reasons for penalties. That is data the whole server should not see, and often not even the whole staff.
- Name a log access role — automatic setup sets its permissions on the log channels.
- @everyone should not have View Channel in the log category.
- Decide who has access to the Deleted messages category — it is the most sensitive set.
Require a reason on every penalty
Panel → Server → General settings/warn <user> [reason]A log without a reason does not help during an appeal. A reason typed once stays in the history and saves later discussion.
- You set the moderation log channel in Panel → Server → General settings.
- The /warn, /mute, /kick, /ban and /temporary-ban commands all take a reason parameter.
- The Penalty history context menu shows earlier entries without leaving Discord.
Review a member's history
Panel → Moderation → Member profilesA member's profile gathers their activity, cases, applications and incidents in one place. That is a faster route than searching through log channels.
- On Discord the same shortcut comes from the message context menu → Apps → Penalty history.
- The Moderation centre card shows the warnings, with the option to remove them.
- If you use the MSIoU network, check Panel → Moderation → MSIoU network too — it synchronises warnings, kicks and bans between servers.
Set your data retention rules
/retention [days] [dry-run]Keeping everything forever is needless risk. The /retention command lets you check and remove the server's old data, and the dry-run parameter first shows what would be deleted.
- Run it with dry-run first, to see the scope without deleting anything.
- Agree a retention period and write it into the server's rules or privacy policy.
- The command requires the Administrator permission.
The steps you tick are saved in your browser — you can come back and finish later.
Verification
How to check the configuration worked
- 1
Warn a test account and check that the Moderation category carries an entry with the member, the moderator and the reason.
- 2
Delete one of your own messages and check the Deleted messages category.
- 3
Grant and remove a role — the Roles category should record both changes.
- 4
Check from an account with no staff role that the log channels are invisible.
- 5
Run /retention with the dry-run parameter and make sure the report shows the expected scope of data.
Diagnostics
When something does not work
The log channel is empty despite the actions taken.
- Cause
- The category is off, has no channel assigned, or the bot cannot write in it.
- Fix
- Panel → Moderation → Logs: check the switch and the channel on the category, then the bot's permission to send messages there.
Everything lands in one channel and nothing can be found.
- Cause
- Every category points at the same channel.
- Fix
- Split at least penalties, deleted messages and voice events into separate channels. Automatic setup does that immediately.
The whole server can see the logs.
- Cause
- No log access role was set, and the channels inherit permissions from a public category.
- Fix
- Set a Log access role and take View Channel away from @everyone in the log category.
Discord's audit log has no older entries.
- Cause
- Discord keeps the audit log for 45 days — older entries are removed.
- Fix
- For a longer history use the bot's log categories, which record events in the server's channels and stay there until you delete them.
Honestly
What this configuration does not solve
The bot will not log an event that happened before it joined the server, or while it was offline.
Discord's audit log has a 45-day retention and contains no message content — no bot gets around that limit.
Message logs work on the channels the bot has access to. Private channels without the bot will not be logged.
Venon does not log private messages between members.
Logs are personal data under the GDPR. Agree a retention period and describe it in the server's privacy policy — the /retention command helps enforce it, but it does not replace the administrator's decision.
Commands
The commands used in this guide
Read on
Related guides
How do you clear spam on Discord?
How to clear spam on Discord: the /clear command, muting the author, the log entry and the AutoMod settings that stop it coming back.
Read the guideHow do you set up AutoMod on Discord?
How to set up AutoMod on Discord: anti-spam, anti-caps and mention-limit thresholds, word blacklists and actions per detector. With a test and the usual mistakes.
Read the guideWhich Discord moderation bot speaks Polish?
How to pick a Polish-speaking Discord moderation bot: the list of requirements, what to compare, and what Venon Security does and does not do.
Read the guide
FAQ
FAQ – common questions
Who should have access to the moderation logs?+
Only the people responsible for moderation and administration. Logs contain the content of deleted messages and the reasons for penalties, so wide access is both a leak risk and a temptation to browse other people's conversations for no reason.
How long does Discord keep the audit log?+
45 days. After that the entries disappear and cannot be recovered. That is why a longer history has to be built on the bot's log channels, which stay on the server until you delete them.
Can you see the content of a deleted message?+
Yes, if the Deleted messages category was on at the moment of deletion and the bot had access to the channel. Messages deleted before logging was enabled cannot be recovered.
How do you remove the server's old data?+
With the /retention command and its days parameter. Run it with dry-run first, to see what would be deleted. The command requires the Administrator permission.
Set this up in your own Venon Security panel
Every screen mentioned in the guide is in the web panel. You save the configuration by hand and see its state before anything takes effect on the server.