Feature
Audit Logs
See who changed members, teams, keys, and AI settings, with the user, action, entity, time, and affected resource on every entry.
Actor
User
Entity
Key + team
Action
Changed
Administrative changes to access and policy, separate from model request traffic.
Actor
Admin
User who made the change.
Action
Policy updated
Setting change recorded with time.
Resource
support-prod
Affected key or team.
New capabilities
What your team gains with Concentrate
Know who changed what
See the user behind every change to settings, keys, members, teams, and access, so a policy change always has a name attached to it.
Tie actions to resources
Connect each action to the entity it touched, like the specific key, team, or setting that changed, with a timestamp.
A record your reviewers trust
Give security and operations a reviewable trail for access reviews and incident write-ups, instead of reconstructing events from memory or chat history.
Who Concentrate is designed for
What audit logs cover, and what they don't
Audit logs record administrative changes: who invited a member, who tightened a key limit, who changed model access or retention. Request logs record model traffic. Security reviews need both: configuration history, and proof of who can change it.
Security and compliance
Show reviewers who changed access, spend limits, logging, and data-handling settings, with timestamps and affected resources.
IT and admin teams
Trace a policy change to the actor instead of reconstructing events from chat or memory.
Incident write-ups
Pair audit entries with request logs when an access change coincides with unusual traffic.
Separation from request logs
Request logs are traffic; audit logs are control-plane changes. Different questions, different audiences.
Feature basics