Export the audit log for compliance
The audit log can be exported for an external auditor or your own records. Two exports exist on the Audit Log page (Pro plan):
- Export CSV / JSON / PDF — a quick client-side download of the rows currently in view.
- Compliance CSV — a server-generated, admin-only export with the stable column set auditors expect. Use this one for compliance evidence.
Run a compliance export
- Open Audit Log.
- Set the From / To date range (and optionally pick a single agent in the Agent filter — the export honours both).
- Click Compliance CSV.
The download is generated by the proxy (GET /v1/audit/export), scoped to your
organisation, and is admin-only — members get a 403. It is independent of
the page’s pagination, so it captures the full range, not just what’s on screen.
Columns
The CSV has a fixed, documented column order so downstream tooling can rely on it:
timestamp, owner_id, agent_id, platform, action, result, reason,
policy_id, policy_version, pii_detected, pii_redacted, pii_categories,
correlation_id- reason — the deny/approval reason code when present (e.g.
endpoint_scope_mismatch,denied_by_guardrail). - policy_id / policy_version — which user policy version decided the call, so a year from now you can answer “what was this person allowed to do then?”
- pii_* — whether PII was detected/redacted and which categories.
- correlation_id — the request id, to tie a row back to a specific call.
Filters & limits
Query filters: date range, a single agent, a single platform, and result
(allowed / denied / pending_approval / error / suspended). JSON format
is also available (?format=json) and returns { count, truncated, filters, rows }. Very large ranges are capped; if truncated is true, narrow the date
range and export in slices.