Governance
Audit log
Every change to how your organization is set up is recorded: who made it, when, from which IP address, and what changed, with the value before and after. Request logs tell you what your agents did; the audit log tells you who changed the rules they run under.
What's recorded
| Area | Changes |
|---|---|
| API and admin keys | Created, revoked, disabled or enabled, limits changed (spend caps, rate limits, max $ per run), MCP servers changed |
| Provider keys | Added, replaced or removed, with the key's last characters only |
| Guardrails | Patterns added, removed, turned on or off; library rules turned on or off; moderation on or off |
| MCP allowlist | Servers added, changed or removed (URL without its query string) |
| Organization | Spend caps and rate limits, routing, tier overrides, prompt persistence, cache wipes |
| Team | Invitations sent, cancelled and accepted; role changes; members removed |
| Billing | Switching from a BYOK trial to credits |
Changes made through the platform API with an admin key are recorded with that key's name as the actor. Actions Leanroute takes on your account, such as disabling an organization, appear as “Leanroute”.
What's never recorded
Secrets. API key values, provider keys and MCP authorization tokens are never written to the audit log: keys appear by name and prefix or last characters, and MCP server URLs without their query string.
Where to see it
In the dashboard under Audit log, filtered by time and by area. Owners and admins can see it; members can't. Export CSV downloads the current filter (up to 10,000 entries) with the time in UTC, the actor, the action, the target, a readable summary and the full details as JSON.
How long it's kept
For as long as your organization exists. Entries can't be edited or deleted from the dashboard or the API. Deleting the organization deletes its audit log with it.
Limits
- Changes start being recorded on 20 November 2026. Earlier changes aren't in the log.
- The log records changes after they're made. There's no approval step before a change takes effect, and no one-click rollback.
- Sign-ins are not recorded in the audit log.
For how this fits a governance programme, see AI governance and the MAS AI Risk Management Guidelines mapping.