Activity and audit log
See every request made through the gateway and who made it, read stored conversations, and review every administrative change.
ACOG keeps two records: the Activity page, of requests through the gateway, and the Audit log, of changes to your organization’s configuration.
Activity
Activity lists every request your organization made through the gateway, newest first, and who made it. Filter by application, user, team, outcome, tokens and cost, over a time window.
Open a request to see:
- The request: who, which key and application, when.
- Which model answered: the model requested, the model that served it, whether auto mode chose it, your default model, and the routing saving.
- Tokens: used, what would have been used, and tokens avoided.
- Timing and outcome: total latency, the provider’s share and ACOG’s overhead, and any provider error.
Stored conversations
When prompt storage is on, the request also shows the conversation: the prompt and the reply. Streamed replies are marked as not scanned.
| Setting (Admin → Gateway settings → Store prompts for review) | Default |
|---|---|
| Store prompts for review | On |
| Delete after | 30 days (1 to 365) |
Turning it off stops storing new conversations. Stored conversations are deleted when they reach the retention period. A change affects only requests made after it.
Who can see Activity
Activity requires the See every request made through the gateway, and by whom permission (audit:conversations). Only people signed in to the console can hold it: no API key and no custom role can carry it. Every view of a stored conversation is itself recorded in the audit log.
Audit log
Admin → Audit log lists every change to your organization’s configuration, newest first: who made it, when, the action (create, update or delete) and what it changed, for example monthly_limit_usd 25000 → 30000. Expand an entry for the actor’s role, the exact time, the API endpoint, the source IP and a before-and-after table.
Search covers the whole log, not only the page on screen. Filter by actor and by kind of entity.
Impersonation (an admin viewing the console as another member) is recorded at start and end, with both identities.
The audit log requires View invoices and billing status (read:billing).