Audit logs
A record of who changed members, teams, keys and settings, and when.
What is Audit logs?
Audit logs record who changed members, teams, API keys and AI settings, with the user, the action, the entity and the time. Spro's audit logs for account changes are planned and not yet available. Today, guardrail decisions are recorded in the usage log.
When a key is revoked or a guardrail is switched off, someone needs to know who did it. An audit log answers that question for every settings change, not only for requests.
This page describes planned behaviour. The events covered and how long they are kept will be published with the feature.
Key features
What this feature does for your requests.
- Entries for member, team, key and setting changes
- Who made each change and when
- The entity and what changed
- A record for security and compliance reviews
How it works
4 steps, from setup to the first request.
- 01
A change is made
Someone edits a key, a member or a setting.
- 02
An entry is written
The user, action, entity and time are recorded.
- 03
Review the log
Filter the log to the change you are checking.
- 04
Use it in reviews
Show the record in a security or compliance review.
Is it the right fit?
Specific situations where this feature helps, and where it does not.
Good fit if
- Security reviews need evidence of who changed keys or guardrails
- A team needs to trace an unexpected setting change
- Compliance requires a record of administrative actions
Not a good fit if
- You only need the record of AI requests. Request logs cover that
- A small team where everyone knows who changes what
- You need the audit log today. This feature is not yet available
Audit logs FAQs
Common questions about Audit logs.
Route every AI request through SPRO.
One OpenAI-compatible API for 350+ models, with intelligent routing, 29 built-in guardrails, observability, and automatic failover.
