Most servers add a logging bot after something goes wrong: a message disappears mid-argument, a role gets handed out that should not have been, or a mod quietly bans someone. Before you add one, it helps to know what Discord already records, because the audit log covers more than people think and less than they hope.
What Discord's audit log already does
Every server has an audit log under Server Settings. Anyone with the View Audit Log permission can read it. It records administrative actions with who did them: bans, kicks, timeouts, role and permission changes, channel edits, invites created, bots added, and message deletions. Entries are kept for 45 days and then drop off.
What it does not keep is content. A message deletion entry tells you a message was deleted in a channel and how many, not what it said. Message edits are not in the audit log at all, and neither are ordinary joins and leaves. That gap is the job of a logging bot.
Audit log vs logging bot
| Event | Audit log | Logging bot | Bot needs |
|---|---|---|---|
| Message deleted | That it happened, channel, count | The text, if the bot saw the message first | Message Content intent |
| Message edited | Not logged | Before and after, if it saw the original | Message Content intent |
| Member joined or left | Not logged (bots added are) | Every join and leave, with account age | Server Members intent |
| Ban, kick, timeout | Yes, with the moderator | Yes, often with the reason | Audit log access |
| Role or permission change | Yes, with who changed it | Yes | Audit log access |
| Voice join, leave, move | Only moves and disconnects by mods | Every join, leave and switch | Voice states |
| How long it lasts | 45 days | As long as the channel and the bot keep it | Nothing extra |
Message Content and Server Members are privileged intents: the bot's developer has to switch them on, and bots used by a lot of people need Discord's approval to keep them. A logging bot that cannot get Message Content can tell you a message was deleted but not what it said. The full picture of how that works is in how a bot logs deleted messages.
How to choose a logging bot
There is no single best logging bot. Check these points against the ones you are considering:
- Events covered. At minimum: message edits and deletes, joins and leaves, bans and kicks, role changes. Voice and invite logs are useful for bigger servers.
- Per-event channels. Busy servers want joins in one channel and message logs in another, or nobody reads either.
- Ignore lists. You should be able to skip bot channels, spam channels and staff channels.
- Data handling. A message logger stores your members' messages. Look for a privacy policy that says what is stored and for how long.
- Maintenance. A bot that has not been updated in a year will break the next time Discord changes something.
- Dashboard or commands. A web dashboard is easier for setup; slash commands are fine for small servers.
Free, hosted or from GitHub
Many multipurpose moderation bots include a free logging module. Dedicated logging bots usually offer more events, and some charge for longer history. Open-source logging bots on GitHub let you host the bot yourself so the stored messages never leave your machine, but then you run the server, apply updates, and keep the bot token secret. Anyone with the token controls the bot. Never paste it in a channel or a public repo.
Set up a log channel
- Create a category called
staffand a channel inside it such as#mod-logs. - Deny View Channel for
@everyoneand allow it for your mod role only. - Invite the bot with the permissions it asks for, then allow it to view and send messages in the log channel.
- Turn on the events you want, and send each group to its channel if the bot supports it.
- Add your bot, spam and staff channels to the ignore list.
- Test it: edit a message, delete one, give yourself a role and take it away. Check each one shows up.
- Pair it with AutoMod. Discord's built-in AutoMod can block keyword and spam messages and send an alert to a channel, which pairs well with the same log channel.
Tell your members
Logging message content means keeping copies of what people wrote, including things they chose to delete. Say so in your rules: what is logged, who can read the logs and how long you keep them. It is fairer, and it stops the "you can see deleted messages?" surprise during a dispute. If people ask whether Discord itself reads their messages, point them to what Discord says it monitors.
Where VaultCord fits
Verification logs, not message logs
VaultCord is not a message logger and will not replace one. What it logs is the front door. Verification logs and webhook logs to Discord, with IP, email, location, browser and badges (Premium and Plus). You build the log message in a visual editor with a live preview, and it posts into your log channel next to your logging bot. On Premium and Plus you also get an email if the server is deleted. See the full monitoring overview.
Open the VaultCord dashboard