Audit log
AdminCP > Users > Sunset > Audit log.
Every tier transition, every policy execution, every reactivation, every retention purge writes an audit row. The audit log is the GDPR receipt for the add-on: even after a member is hard-deleted, the action record remains (with PII scrubbed) until the audit-log retention window expires.
Filtering
The filter form supports:
| Field | What it filters on |
|---|---|
| Member | Username token (resolves to a user id) or a raw user id. |
| Event type | One of: Tier transition, Policy applied, Policy skipped, Policy failed, Reactivation, Reactivation request, Reactivation blocked, Snapshot restored, Retention purge. |
| From tier | Source tier of a transition event. |
| To tier | Destination tier of a transition event. |
| Date range | Two date inputs with quick links: Today, Last 7 days, Last 30 days, Clear. |
The reset link in the block footer clears every filter back to the default.
Row anatomy
Each row shows the timestamp, the event sentence (in journal voice), the affected member, the actor (system, admin, user) with username when applicable, and a severity stripe coloured by tier. Two per-row actions:
- Filter by user sets the member filter to that row's user id.
- View user state opens AdminCP > Users > (edit) > Actions > Sunset state for the affected member. Skipped silently if the member has since been hard-deleted (the row's
user_idis scrubbed in that case).
CSV export
The Export button (top right) streams the currently-filtered rows as CSV. The export is paginated by log_id in 1000-row chunks and flushes each chunk before fetching the next, so memory stays flat regardless of how large the audit log is. The columns are structural keys (log_id, created_date, event_type, user_id, username, …) rather than localised labels.
Erasure-scrubbed rows
When a member is hard-deleted from XenForo, their audit rows are scrubbed in place: user_id, actor_user_id, and detail are nulled, erasure_scrubbed is set to 1. The row still shows in the log with the timestamp, event type, and tier information, but no PII remains. These rows survive until the audit-log retention window prunes them.