All featuresServer Management

Audit Logs

Who deleted that channel, and when? FlaviBot names the member behind each change made in Discord, in the channel you choose.

Events only the audit log knows

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.

Filters for the noise

Exclude channels, roles or members, leave bot actions out, which is the default, and keep log posts silent so they never ping anyone.

New account warning

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.

Bursts stay readable

Events that arrive in the same short window, like a purge, are grouped into a single log message instead of one post each.

Questions about Audit Logs

What is the difference between audit logs and the mod-log?

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.

What permissions does FlaviBot need for logs?

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.

Ready to try it out?

Add FlaviBot to your server and start using this feature for free.