Audit Log
See who changed which dashboard setting and when, across every configurable feature.
How it works
The Audit Log is a Premium dashboard page showing a chronological trail of dashboard-driven settings changes: which feature changed, the specific field, its before and after value, who made the change, and when. It complements Logging, which covers Discord activity, by covering the dashboard itself.
Before you start
- An active server Premium subscription — the trail keeps recording even if Premium lapses, but viewing it requires an active subscription.
- No additional setup: every dashboard feature that writes settings is covered automatically.
Configure it
- Open Audit Log in the dashboard.
- Review recent entries, most recent first.
- Change one setting in any other feature, then reload Audit Log to confirm it appears.
What it covers
- Every dashboard feature that saves settings — moderation, verification, economy, reaction roles, and the rest — records to the same trail.
- Only the fields that actually changed are recorded, each as its own before and after pair.
- The trail is per server and only shows changes for the server you are viewing.
Expected result
- A settings change made from the dashboard appears as a new entry listing the changed feature, field, before and after value, and the signed-in account that made it.
- An entry made by an automated process (such as a premium purchase applied by Stripe) shows no personal actor, since no dashboard session made that change.
Common errors
An entry shows an unknown actor
This is expected for changes applied by an automated process rather than a signed-in dashboard session. If a change you made yourself shows no actor, contact support with the approximate time so it can be investigated.
Saved changes do not take effect
Reload the feature page and confirm the saved values. Then verify that the selected Discord channel or role still exists and that Airwavy can access it.
Discord reports missing permissions
Check the permission on both the server role and the target channel. Channel overwrites and role hierarchy can deny an action even when the server-level permission is present.