Audit log
Volvox.Bot records important bot and dashboard actions in the audit log. Use it to review what happened, who triggered it, and what was affected.What it logs
- Moderation actions — Warns, bans, kicks, timeouts, unbans, temp bans, and soft bans
- Classic spam detections — Alert/delete outcomes, message links, channel IDs, and redacted content previews
- Config changes — Who changed what setting, with before/after config details when available
- AI auto-mod decisions — Action taken, model, scores, thresholds, skipped actions, message link, and case number
- Triage alerts — Moderation flags and budget-limit alerts
- DM delivery failures — Member DMs the bot could not deliver for moderation notifications or level-up actions
- Dashboard/API mutations — Successful mutating dashboard requests with masked request details
Settings location
Audit Log settings are in Settings -> Moderation & Safety -> Audit Log.How to use
- Open the dashboard -> Audit Log for your server.
- Filter by category, action, user, target, channel, or date range.
- Select any entry for human-readable details and raw JSON.
Volvox.Bot retains audit logs for 90 days. Contact support if you need longer retention.
Audit log dashboard
The Audit Log page at/dashboard/audit-log is the dashboard reader for audit entries. It includes category, action, user, target, channel, and date filters, plus expandable structured details for each entry.
Use it when you need evidence for a moderation action, config change, ticket event, AI auto-mod decision, triage alert, or failed DM notification.
Audit log settings
The Audit Log settings tab at/dashboard/settings/moderation-safety?tab=audit-log controls audit-log retention for moderation evidence and dashboard/API mutation history.
Filtering
| Filter | Description |
|---|---|
| Category | Moderation, AI and triage, Config, Members, Tickets, or Notifications |
| Action type | Exact actions such as mod.ban, spam.detect, ai_automod.timeout, ai_automod.case_failed, notifications.dm_failed, or config.update |
| User | Filter by who performed the action |
| Target | Filter by who or what the action targeted |
| Channel | Filter spam, AI auto-mod, and triage entries by channel |
| Date range | Focus on a specific time period |
ai_automod.timeout, ai_automod.case_failed, or ai_automod.provider_failed without scrolling the full list.
Reading an entry
Each row leads with a plain-language summary so you can scan the table without decoding action codes. Examples:Mod#0001 banned BadUser#1234, Spam detected from SpamBot#0001, or AI auto-mod timed out SpamBot#0001. Expand a row to see structured panels tailored to the action type:
- Moderation entries show the case number, the action taken, and the reason.
- Spam entries show whether the bot alerted moderators, deleted the message, and where the original message lived.
- AI auto-mod entries show the model used, the categories that flagged the message with their scores, and the configured thresholds. They also include any skipped actions, a link to the original Discord message, and the case number.
- Config changes list the keys that changed in the summary line, so you can spot which setting moved without opening the row.
DM delivery failures
Volvox.Bot DMs members for configured moderation notices (warn, timeout, kick, and ban) and level-up actions. Discord sometimes refuses the delivery because the member has server DMs disabled, has blocked the bot, or shares no other mutual server. When that happens, the bot records a notifications.dm_failed entry instead of swallowing the error. The original action — the ban or the level-up role grant — still runs.
Each entry captures:
- Target — the member the bot tried to DM
- Source —
moderation_dm_notificationorlevel_up_action - Error — the Discord error message returned for the failed delivery
- Details — source-specific context, such as the moderation action and reason or the level reached