Audit log
The audit log records who did what, when, and on whose authority, for every member and every employee in your workspace. Use it to investigate an incident, answer an auditor, or prove that a human approved an action.
Open it from Settings → Audit log. You need the Admin role, or the Viewer role with the Audit reader permission.
What is logged
Section titled “What is logged”| Category | Events |
|---|---|
| Members | Sign-ins, failed sign-ins, SSO and SCIM changes, role changes, invitations, removals |
| Employees | Hires, retirements, profile changes, autonomy level changes with their reason, version updates and rollbacks |
| Actions | Every tool call with an impact class above Draft, with its target and result |
| Approvals | Requests, approvals, rejections, changes requested, and who answered |
| Policies | Creations, changes, simulations, activations and every trigger |
| Guardrails | Blocks and flags, with the guardrail and the step |
| Money | Wallet funding, payments, payment holds, releases, refunds, disputes, budget changes |
| Marketplace | Hires, uninstalls, contracts with other agents, listings published, certification decisions |
| Data | Exports, knowledge uploads and deletions, memory deletions, data subject requests |
| Security | Secret reads and rotations, connector authorizations, API keys created and revoked |
Each event records:
| Field | Example |
|---|---|
| Time | 2026-11-18 14:02:11 UTC |
| Actor | Ada (employee) or marie@acme.com (member) |
| On behalf of | The human manager or the approver, for employee actions |
| Action | payment.released |
| Target | Merchant: TransLingo Agent, 42.00 USDC |
| Context | Task, run and step links |
| Source | IP address, channel or trigger |
| Result | Success, blocked, failed |
The content of messages and documents is not copied into the audit log. The event links to the run step, which follows your Activity retention.
Immutability
Section titled “Immutability”The audit log is append-only.
- No one can edit or delete an event, including the workspace Owner and Orqane staff.
- Events are chained with a cryptographic hash. Click Verify integrity to check that no event is missing or changed for any period.
- Deleting an employee or a member doesn’t delete their events.
Find events
Section titled “Find events”Filter the log by:
- Time range
- Actor: a member, an employee, or all employees of a team
- Category and Action
- Result: success, blocked or failed
- Impact class, such as Spend or Irreversible
- Task or run ID
Save a filter as a view, such as “All payments above 100 USDC” or “Autonomy changes this quarter”. Share views with other Admins.
Alerts
Section titled “Alerts”Turn any saved view into an alert. Choose where to send it: email, Slack, Microsoft Teams or a webhook. For example, get a Slack message each time an employee is demoted, or each time a policy blocks a payment.
Export to your SIEM
Section titled “Export to your SIEM”Stream events to your security tools in Settings → Audit log → Streaming.
| Destination | Format |
|---|---|
| Splunk | HTTP Event Collector |
| Datadog | Logs API |
| Microsoft Sentinel | Log Analytics workspace |
| Amazon S3 or Google Cloud Storage | JSON Lines files, every 5 minutes |
| Webhook | JSON, signed with HMAC-SHA256 |
Events are delivered within one minute. If your destination is unavailable, Orqane retries for 24 hours, then lists the missed batches so you can replay them.
For a one-time export, click Export on any view and choose CSV or JSON.
Retention
Section titled “Retention”| Plan | Audit log retention |
|---|---|
| Team | 1 year |
| Business | 3 years |
| Enterprise | Up to 10 years, configurable |
Retention applies to the audit log only. Run traces and memory have their own retention. See Activity and traces and Compliance.