Audit Log
Every action taken through Arkanis is automatically recorded in the audit log. Track who did what, when, and to whom, with powerful filtering by action type, actor, target, and date range.
Open Audit Log →
Filter, search, and review your moderation team's history. Track who did what, when, and to whom, with powerful filtering by action type, actor, target, and date range.
What is this?
A timeline of every state-changing action Arkanis records: strikes, bans, warnings, configuration edits, RCON commands, role changes, panel edits. Each row identifies the actor, the target, the action, and a plain-English summary of what changed. Filters narrow the list by action type, actor, target, or date range.
Why you might want it
When a moderator decision is challenged six months later, you need to reconstruct it. When a setting is wrong, you need to know who changed it. When a new staff member starts, you want to spot-check their first week. There is nothing to enable; logging is always on, retained indefinitely, and the row identity is searchable.
What Gets Logged
The audit log captures every meaningful action taken through Arkanis, creating a complete trail of staff activity. This is a passive system; there is nothing to enable or configure. Logging is always on.
- Enforcement actions — strikes issued, strikes removed, bans applied, bans lifted, warnings sent, mutes applied
- Player actions — ID linking, ID unlinking, player profile edits, notes added
- Case operations — cases created, claimed, closed, reopened, participants added or removed, appeals processed
- Moderation actions — announcements sent, role panels created or modified, AutoMod rules changed
- Role changes — admin roles assigned, presets changed, capability overrides added or removed
- Configuration changes — features toggled, channels reassigned, settings modified, setup wizard runs
- Server operations — RCON commands executed, Pterodactyl power actions, file operations, log monitoring changes
Using the Dashboard Viewer
The audit log viewer shows every action as an identity-first row: who performed it (display name, authority tier, Discord role at action time), who or what was affected, and a plain-English summary of what changed. Click Audit Log in the sidebar to open it.
Read the Row Identity
Every row reads like a sentence: action label · by · actor display name · tier chip · on · target. The tier chip shows the actor's authority at action time (Owner, Admin, Mod, Member, or System for scheduled actions like log ingestion or background sweeps). For human actors, the searchable username is rendered next to the display name in parentheses when the two differ (e.g. Blytz (@.blytz.)).
Filter by Action Type, Actor, Target, or Date
Use the controls above the timeline to narrow results. The action-type dropdown is the fastest way to scope (e.g. "Strike Issued", "Config Changed"). The actor and target search boxes are debounced so they don't fire on every keystroke. The from/to date pickers narrow results to a specific window for incident review.
One-Click Filter from a Row
The funnel icons on the right side of each row (next to the timestamp) filter the timeline by that exact actor or target in one click. The actor filter intentionally uses the searchable username (e.g. .blytz.) rather than the display name, because two users can share a display name but only one can hold a given username, so the filter scopes to that specific account every time.
Inspect an Entry
Click any row to expand it. The expanded card shows three sections: a Performer block with full identity (display name, tier chip, searchable username, Discord ID with a copy button, and the literal Discord role at action time); a Target block when applicable; and a plain-English summary describing what happened. Configuration changes use cardinality-aware phrasing (e.g. Added "xbox" to Players → Supported Id Types. Now allows: steam, xbox.) instead of raw before/after JSON.
Show Raw Details When You Need Them
The plain-English summary covers the common case, but the full details payload is one click away. Use the Show raw details toggle at the bottom of each expanded row when you need the underlying JSON for debugging, exports, or precise field-level review. The toggle is per-row (collapsing one doesn't collapse others) and resets when the row itself is collapsed.
Best Practices
The audit log is your primary accountability tool. Here are some ways to get the most out of it.
- Regular reviews — periodically check the audit log to ensure staff actions align with your community guidelines and moderation policies
- Incident investigation — when a community member reports unfair treatment, use the target filter to pull up their complete action history
- Onboarding verification — after adding new moderators, review their first few days of activity to ensure they understand your processes
- Configuration tracking — if a setting seems wrong, filter by "Config Changed" to see who changed it and when
- Compliance — use date range and action type filters to export evidence of enforcement decisions if disputes escalate