Server logs
Server logs answer the question every staff team eventually asks: who deleted that channel, and when? FlaviBot watches your server and writes each event down as a compact message in a log channel.
This is separate from the mod-log. The mod-log records what your moderators did through FlaviBot. Server logs record what happens on the server itself, including changes made directly in Discord by people who never touch the bot.
Everything below is on the dashboard's Server Logs page.
Turning it on
Flip Enable server logs, then pick a default log channel. That channel is the fallback for every category you do not route elsewhere.
The bot needs three permissions there: Send Messages, Embed Links and Manage Webhooks. The last one is not optional: logs are delivered through a webhook FlaviBot creates in the channel, which is what lets a burst of events post quickly without hitting Discord's rate limits. The messages still appear under your bot's name and avatar.
Forum and media channels work, but you must also pick the specific post inside them, otherwise there is nowhere to deliver.
Choosing what to log
Log all events is on by default, and means exactly that: every event in every category below.
Untick any single event and the switch flips to a custom list, starting from everything and minus what you removed. Untick everything and the page warns you that nothing will be logged, since that is almost never what someone meant to do.
What each category records
| Category | Events |
|---|---|
| Messages | message deleted, edited, bulk deleted, pinned, unpinned |
| Members | joined, left, nickname changed, roles changed, avatar changed, timed out, timeout lifted, started boosting, stopped boosting |
| Moderation | banned, unbanned, kicked, pruned, AutoMod action taken, AutoMod rule created, updated or deleted |
| Roles | role created, updated, deleted |
| Channels | channel created, updated, deleted, permission overwrite created, updated or deleted, thread created, updated, deleted |
| Voice | joined a voice channel, left, moved between channels |
| Server | server settings updated, emoji created, updated or deleted, sticker created, updated or deleted, soundboard sound created, updated or deleted, onboarding updated |
| Invites | invite created, invite deleted |
| Integrations | webhook created, updated or deleted, integration created, updated or deleted, command permissions updated |
| Events | scheduled event created, updated, deleted, stage created, updated, deleted |
A member join line also carries the account's creation date, the server's member count, and the invite code plus the inviter when FlaviBot can attribute the join.
The audit log badge
Some events are marked Audit log in the dashboard. Discord does not announce those over the normal event stream, they exist only as audit log entries, so the bot needs the View Audit Log permission to see them at all. Kicks, prunes, permission overwrite changes, pins, emoji, sticker, soundboard, webhook, integration and onboarding changes are all in this group.
The audit log is also where the who comes from. For an event like a ban or a role change, Discord's raw notification says what changed but not who did it, so FlaviBot pairs the two and adds the responsible member to the line.
Routing categories to different channels
By default everything lands in the default channel. You can give any category its own channel, which is how most servers separate a noisy message log from a quiet moderation log.
The number of distinct channels you may use depends on your plan:
| Plan | Distinct log channels |
|---|---|
| Free | 1 |
| Silver | 5 |
| Gold | 10 |
| Platinum | 15 |
The page shows your current count next to the limit, and saving is rejected if you go over it rather than silently dropping a route.
Filters
Under Advanced filters:
- Exclude channels: activity in them is never logged
- Exclude roles: events caused by a member holding any of them are skipped
- Exclude members: same, for specific people
- Log bot actions: off by default, since bots generate most of the noise
- Silent messages: on by default, so log posts never ping anyone
- New account age: set a number of days and any member joining with a younger account is flagged on their join line, which is your early warning during a raid
Bursts
A purge or a raid can produce dozens of events per second. FlaviBot groups what arrives within the same short window into a single log message rather than posting each one separately, so the channel stays readable and delivery keeps up.
