Audit records
Path: /org/audit
Audience: owners and administrators. Administrator-only. Individual API calls are in Request logs — a different thing entirely.
What is recorded
Audit covers administrative actions, not API calls:
- member creation, changes (role / quota / state), suspension and removal;
- invitation creation and revocation;
- enterprise balance adjustments;
- changes to Settings.
Each record carries the actor, the action, the target and the time — enough to answer “who changed this member record, and when”.
Only non-sensitive context
Audit does not record passwords, verification codes, keys, or invitation token plaintext. You will not find “what the key was” here — that is deliberate, not missing.
What you cannot see here
Platform operator actions do not appear in enterprise audit records. Platform-side review, suspension and quota adjustments of an enterprise are recorded on the platform side and are not visible here. Enterprise audit covers the enterprise’s own scope.
So an empty audit view does not prove nothing happened. Contact the platform if you need to reconcile platform-side operations.
Versus request logs
| Audit records | Request logs | |
|---|---|---|
| Subject | Administrative actions | API calls |
| Who appears | Enterprise administrators and members | Whoever used the key |
| Amounts | Balance adjustments carry amounts | Every call carries its charge |
Related
- Request logs — API calls
- Members · Invitations · Settings — the pages recorded here