Discord Moderation Logs & Audit Trail
Discord moderation logs give your team a single record of every enforcement action. LoggerBot logs bans, unbans, kicks, timeouts, and warnings, and reads Discord’s audit log to attach the moderator and the reason where it can.
It complements Discord’s built-in audit log with a persistent, readable feed in a channel you control — and adds a warning system Discord does not have.
LoggerBot✓ App17:51
usheenes0622_01421
Member Banned
- User:
- @NowaK
- Moderator:
- @LoggerBot ( LoggerBot#7074 )
- Reason
- LoggerBot is taking Discord logging to the next level. — requested by mohssy
ID: 1266889469705977968 | Today at 17:51
What LoggerBot logs
- Ban / unban — the target user, the moderator, and the reason from the audit log.
- Kick — who was kicked, by whom, and why.
- Timeout / timeout removed — the member, the moderator, the reason, and when the timeout ends.
- Warnings — issued with /warn, DMed to the member, and kept in a running warning history.
- Ban evasion — when a previously banned user is detected rejoining under a new account.
How the audit trail works
When a member is banned or kicked, Discord fires an event but does not include who did it. LoggerBot checks the server audit log immediately afterwards to find the matching entry and pull the moderator and reason. If the audit log entry is not available, the action is still logged without attribution rather than dropped.
Leaves are cross-checked against the audit log too, so a kick is logged as a kick and not mistaken for a member leaving on their own.
Setting it up
- 1Enable the Mod Logs category, or the individual ban, kick, timeout, and warn logs.
- 2Open the dashboard, pick your server, and set a main log channel — or run
/setlogallin Discord to create a channel per category automatically. See the getting-started guide. - 3Point Mod Logs at a staff-only channel — keep it separate from voice and member logs so it stays scannable.
Frequently asked questions
Does LoggerBot replace Discord’s audit log?
No — it complements it. Discord’s audit log is short and hard to scan; LoggerBot posts a readable, permanent entry to your own channel and adds warnings on top.
Where does the moderator and reason come from?
From the server audit log. LoggerBot looks up the matching audit entry right after the action. If Discord has not written it yet or the bot lacks View Audit Log, the action is logged without a moderator.
Can I log actions taken by other moderation bots?
Yes. A ban is a ban regardless of which bot or which person issued it. You can exclude a specific bot under Ignore Options if it is too noisy.
Are warnings stored?
Yes. /warn keeps a per-member warning history you can view with /warnings.
Related logging features
Browse all featuresAdd LoggerBot to your server
Set up mod logs in under a minute — pick a channel and you are done. Generous free plan.