Optiak Docs
Compliance

Audit Logs

See who changed what in your organization, and when.

Audit logs record the administrative actions taken in your organization: who changed a policy, a key, a member's access or an application, and when.

Required role

Organization Admin

Applies to

Administrative actions
Optiak records actions across the organization and its applications. Organization Admins can read the log.

Why use it

When an auditor or a security review asks who granted someone access, who rotated a provider key or when a governance policy changed, the audit log answers with a name and a timestamp. You don't have to reconstruct it from chat threads or memory.

  • Accountability. Every entry names the member who acted.
  • Read-only records. You cannot edit or delete audit entries through the console or API.
  • Complete with request records. Audit logs cover changes to the setup; each LLM request and tool call has its own record in Observability. Together they show both who configured the controls and how they acted on traffic.

How it works

A recorded administrative action becomes an audit log entry you can review later.

A member acts

Changes access, settings, an application or a key

Optiak adds an audit log entry

The record identifies the action and the member who took it.

User
Who acted
Operation
What they did
Resource
What they changed
Date
When it happened

Review in Audit logs

Search, sort and filter administrative activity

What is recorded

Audit logs record administrative actions only. The prompts, responses and tool calls your applications send through the Gateway are recorded per request in Observability, not here.

Where to find it

In the console, open Settings, then Audit logs. The menu entry appears only for members who can read the log; see Members and Access for roles.

Entries are listed newest first. Search across users, operations and resources, or sort and filter by User, Operation, Resource and Date. Select refresh to load entries recorded since you opened the page.

Limits and behavior

  • Search and filters apply to the entries currently loaded in the page.
  • Request traffic isn't in the audit log. Use the application's Requests tab for that.
  • Logged actions might not appear immediately. There might be a delay between when operations are performed and when they first show up in the audit logs.
Copyright © 2026