How to Set Up a Mod Log Channel in Discord (Track Every Warn, Mute, and Ban)
To set up a moderation log channel in Discord, create a private text channel (for example #mod-log), lock it so only staff can read it, then connect a logging bot like PeakBot to post every warn, mute, kick, and ban into it automatically with the moderator, target, reason, and timestamp. That gives your team one permanent, searchable record of every action taken on the server.
A mod log is the difference between "I think someone banned that guy last month" and knowing exactly who did it, when, and why. If you run a server with more than one moderator, you need one. Here is how to build it properly.
Why every server needs a mod log
When your server is small, you remember every action because you took all of them. The moment you add a second or third moderator, that breaks down. Someone gets banned and the member appeals, but nobody on staff remembers the reason. Two mods warn the same person for the same thing without realizing it. A moderator quietly removes a message that should have been escalated. None of this is malicious, it is just what happens when actions live only in people's heads.
A dedicated mod-log channel fixes that by writing every moderation action to one place the instant it happens. It gives you three things you cannot get any other way:
- Accountability. Every action is attributed to a specific moderator, so the team holds itself to a consistent standard.
- Continuity. A new mod can scroll the log and immediately understand a member's history before deciding how to handle them.
- Evidence. When a banned user comes back to argue, you have the timestamp, the reason, and often the original message that triggered the action.
If you are still figuring out your broader moderation approach, our complete guide to moderating a Discord server covers the policies that sit on top of your logs.
Native audit log vs a dedicated mod-log channel
Discord already has a built-in audit log under Server Settings → Audit Log. It is useful, and you should not ignore it, but it is not a substitute for a real mod-log channel.
The native audit log records server-level changes: bans, kicks, role edits, channel deletions, and permission changes. Its limits matter, though:
- It only keeps about 90 days of history. Older entries fall off, so you cannot review a member's full track record going back further than a few months.
- It does not reliably log warns or mutes from bots. A warning issued through a bot command often does not appear at all, and a timeout shows up as a raw permission change rather than a clear moderation entry.
- It is not searchable in any meaningful way. You scroll, you filter by a few categories, and that is it. You cannot pull "every action taken against this one user."
- It loses the context that matters. The audit log will not show you the message that caused the ban, because that message is already deleted by the time you look.
A dedicated mod-log channel, fed by a bot, solves all of that. It is permanent, it captures bot-issued warns and mutes, it preserves deleted message content for context, and you can use Discord's own search bar to find every entry mentioning a specific user ID. Use both: the audit log for raw server changes, your mod-log channel for the human moderation story.
Step 1: Create the mod-log channel
In your server, open the + next to a category (a staff-only category is ideal) and create a new Text Channel. Name it something obvious like mod-log, mod-logs, or staff-log. Avoid cute names. When you are scanning during an incident, you want to find it instantly.
If your server is busy, consider splitting logs into two or three channels later: one for moderation actions (warns, mutes, kicks, bans), one for message edits and deletions, and one for joins and leaves. For most servers, a single channel is the right place to start.
Step 2: Lock the channel down to staff only
This is the step people skip, and it matters. Members should never see your mod log. It exposes moderator decisions, reasons, and member history that can fuel drama.
Open the channel's settings, go to Permissions, and set it up like this:
- Select the @everyone role and turn View Channel to the red X (deny).
- Add your moderator and admin roles and turn View Channel to the green check (allow).
- For the staff roles, also deny Send Messages so nobody accidentally posts in the log and clutters it. The bot will post regardless because bot permissions are handled separately.
If you want a deeper walkthrough of how allow, deny, and neutral permissions interact across roles and channels, our Discord permissions guide for 2026 breaks down the order Discord evaluates them in. Getting this wrong is the most common reason a "private" channel turns out not to be private.
Step 3: Add a logging bot and point it at the channel
The native audit log cannot post to a channel, so you need a bot to do the actual logging. Invite your bot of choice, then open its dashboard or run its setup command to tell it which channel to use.
With PeakBot, you invite the bot from peakbot.pro, open the dashboard, and set your mod-log channel under the logging settings. Full logging is part of PeakBot's free feature set, so you can track moderation actions without paying for a premium tier. If you are comparing options first, our roundup of the best Discord logging bots for 2026 walks through the trade-offs of each.
Whatever bot you choose, make sure its role sits high enough in your role list to read and post in the locked channel, and that it has View Audit Log, Read Message History, and Send Messages permissions there.
Step 4: Choose which events to log
More is not always better. A log that captures literally everything becomes noise, and noise is just as useless as no log at all. Decide deliberately what belongs.
For a moderation log specifically, prioritize the events that represent an action or a risk:
- Warns — who warned whom, for what.
- Mutes / timeouts — including the duration.
- Kicks — with the reason.
- Bans and unbans — the most important entries to keep forever.
- Message deletions and bulk deletions — especially deletions by moderators, which can hide misconduct.
- Message edits — useful for catching someone who posts something, gets a reaction, then edits it to look innocent.
Events you can usually route to a separate, lower-priority channel (or skip): every member join and leave, every role assignment, every voice channel hop. They have their place, but they bury the entries you actually act on.
Step 5: Log warns, mutes, kicks, and bans automatically
This is the heart of the system. You do not want moderators copy-pasting actions into a channel by hand, because they will forget, and a log with gaps is worse than no log because it gives false confidence.
With a logging bot connected, the flow becomes automatic. When a moderator runs a warn, mute, kick, or ban through the bot's commands (or through Discord's native ban/timeout, which the bot watches via the audit log), a clean entry appears in your mod-log channel. A good entry includes:
- The action type (warn, mute, kick, ban).
- The target user, including their user ID, so the entry survives a name change.
- The moderator who took the action.
- The reason they typed.
- A timestamp, and for mutes, the duration.
PeakBot also pairs this with context-aware AI moderation that reads message intent instead of matching a fixed keyword blocklist, so when it auto-actions something, the log entry tells you what it caught and why. That means even the automated removals leave a paper trail, not a mystery.
Step 6: Review patterns to catch problem members early
A log is only valuable if someone reads it. Build a habit: once a week, or after any major incident, scan the mod-log channel and look for patterns rather than single events.
Use Discord's search bar to pull a single member's full history by searching their user ID inside the channel. That instantly answers the question that matters most during an appeal or an escalation: is this a one-time mistake, or the fifth warning in three weeks?
The patterns worth watching for:
- Repeat offenders racking up warns that individually seem minor but add up.
- One moderator issuing far more actions than the rest, which can signal either a hotspot in the server or a mod who needs coaching.
- Clusters in time, like a wave of bans in one hour, which often points to a raid worth investigating.
Step 7: Tie logs into analytics for the full picture
A raw log tells you what happened. Analytics tell you whether it is getting better or worse. The two together are how you actually run a healthy server instead of just reacting to fires.
PeakBot's analytics dashboard sits alongside its logging, so the same bot that records each ban also shows you trends: are moderation actions rising or falling, which channels generate the most incidents, and when your most active and most chaotic hours are. Seeing a spike in bans line up with a spike in new joins, for example, is often your first clue that a raid is underway, and your mod log gives you the per-action detail to confirm it. Because PeakBot replaces MEE6, Carl-bot, Dyno, and TidyCord with one bot, your logs and your analytics come from the same source instead of separate tools that never quite agree.
Step 8: Keep logs tidy and searchable
A mod log you cannot navigate is just a wall of text. A few habits keep it usable as it grows:
- Always require a reason. "Banned for spam" is searchable and meaningful. A blank reason is dead weight. Configure your bot to demand a reason on moderation commands if it supports it.
- Use consistent wording. If the team agrees to write "raid", "spam", "nsfw", and "harassment" as standard reason tags, you can search the channel by tag and instantly pull every raid-related action.
- Keep IDs in entries. User IDs never change, usernames do. An entry with a raw ID stays findable forever.
- Do not delete the log. Resist the urge to "clean up" old entries. The value of a mod log is precisely that it goes back further than anyone's memory. Archive the channel instead of purging it.
Set this up once and it runs quietly in the background, turning every moderator action into a permanent, searchable record you will be grateful for the first time a dispute comes up.
Frequently asked questions
How do I set up a moderation log channel in Discord?
Create a private text channel such as #mod-log, deny View Channel for @everyone and allow it only for your staff roles, then connect a logging bot like PeakBot and point it at that channel. The bot will post every warn, mute, kick, and ban automatically with the moderator, target, reason, and timestamp.
Can Discord log warns and bans without a bot?
Partly. Discord's native audit log records bans, kicks, and some server changes, but it only keeps roughly 90 days of history, is not searchable per-user, and usually does not capture bot-issued warns or mutes clearly. For a complete, permanent, searchable record you need a logging bot posting to a dedicated channel.
Should members be able to see the mod-log channel?
No. The mod log exposes moderator decisions, reasons, and member history that can cause drama if it is public. Lock it so only your moderator and admin roles can view it, and deny Send Messages even to staff so nobody clutters the channel by hand.
Is logging free in PeakBot?
Yes. Full logging is one of PeakBot's 30+ free features, with no time limit and no trial period. You can track warns, mutes, kicks, and bans in a dedicated channel without paying for the $8.25/month Pro tier, which is reserved for features like the AI Server Builder.
What is the difference between Discord's audit log and a mod-log channel?
The audit log is Discord's built-in, roughly 90-day record of server changes that you cannot search per-user or feed bot warns into. A mod-log channel is a permanent, searchable channel where a bot posts every moderation action with full context, including deleted message content. Use the audit log for raw server changes and a mod-log channel for the complete moderation story.
