Audit Logs answer the question every staff team eventually asks: who deleted that channel, and when? FlaviBot watches your server, pairs each change with Discord's audit log entry to name the member responsible, and writes it as a compact message in the log channel you choose. It records changes made directly in Discord by people who never touch the bot, and it is separate from the mod-log, which records what your moderators did through FlaviBot. Filters leave out channels, roles, members and bots, and members joining with a young account are flagged. The number of distinct log channels depends on the server's plan.
Kicks, prunes, pins, permission overwrites, emoji, webhook and integration changes exist only in Discord's audit log, so FlaviBot needs View Audit Log to record them at all.
Exclude channels, roles or members, leave bot actions out, which is the default, and keep log posts silent so they never ping anyone.
Set an account age in days and every member joining with a younger account is flagged on their join line, an early warning during a raid.
Events that arrive in the same short window, like a purge, are grouped into a single log message instead of one post each.
Every setting explained, step by step.
The numbers FlaviBot enforces. They follow the server's plan, except saved playlists and custom bots, which follow your account's plan.
| Limit | Free | Silver | Gold | Platinum |
|---|---|---|---|---|
| Distinct log channels | 1 | 5 | 10 | 15 |
The mod-log records what your moderators did through FlaviBot. Audit logs record what happens on the server itself, including changes made directly in Discord.
Send Messages, Embed Links and Manage Webhooks in the log channel, since logs are delivered through a webhook FlaviBot creates there. View Audit Log is needed to name who made a change and to record the events that exist only in the audit log.
Add FlaviBot to your server and start using this feature for free.
Add to Discord