> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xenovia.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit logs

> Who changed what, in an append-only log sealed into a hash chain you can verify.

See who changed what in your organization, and prove the record wasn't altered. Every change to an agent, policy, provider or key is recorded, and each record is sealed into a hash chain.

For example, someone moves a policy from Monitor to Enforce. The audit log shows the change, who made it, from where, and its request ID; **Verify chain** confirms no record was changed or removed since.

## Read the log

**Settings › Audit logs** is for admins. Organization API keys can read it through the API too; members and Nova can't.

Each event shows **When**, **Action**, **Resource**, **Actor**, **Source**, **Result** and **Request**. Filter by action (Create, Update, Delete), resource (Agent, Policy, Provider, API key), result, source service (Control plane, Agent runtime), **Who acted** (a person, an API key, a deployment, Nova or the Discovery planner), event, user or request ID, and dates.

Send your own `X-Request-ID` with a management API request to have it recorded on the event. Some changes record their own action names, for example `agent.sub_agent.create`, `neon.settings.update` and `agent.fallbacks.update`, with the values before and after.

![Audit log table with when, action, resource, actor, source and result for three events](https://mintcdn.com/xenovia/RO5UF1Tk8L9B7yPt/images/screens/audit-logs.png?fit=max\&auto=format\&n=RO5UF1Tk8L9B7yPt\&q=85\&s=0e4c4267a73a5d7d863f12d4b85f394c)

Settings › Audit logs

## Verify it

Each event is sealed into a hash chain seconds after it is recorded: each record carries the hash of the one before it. When Compliance is on for your organization, the **Integrity** card shows:

* **Verify chain** recomputes the chain and reports **Intact** or **Broken**. A break says which event is missing, no longer follows the one before it, or was changed after it was sealed.
* **Download signed export** downloads the chain as a JSON file signed with Ed25519, with the public key to check it against. Keep a copy outside Xenovia; the control plane's `scripts/verify_audit_export.py` checks it offline.

A signed export is needed because whoever runs the database could rewrite the whole chain consistently. Exports must be set up on the control plane first; until they are, the card says so.

## With the API

| Endpoint | Returns |
| - | - |
| `GET /api/v1/orgs/{org_id}/audit-logs` | Events, with the same filters |
| `GET /api/v1/orgs/{org_id}/audit-logs/verify` | The chain check |
| `GET /api/v1/orgs/{org_id}/audit-logs/export` | A signed export of up to 10,000 records |
| `GET /api/v1/orgs/{org_id}/audit-logs/signing-key` | The public key exports are signed with |

## What next?

> [card] [Compliance](https://docs.xenovia.io/organization/compliance.md)
>
> Turn the record into evidence for auditors.

> [card] [Users and keys](https://docs.xenovia.io/organization/users-and-keys.md)
>
> Control who can make changes.

> [card] [API](https://docs.xenovia.io/api-reference/introduction.md)
>
> Read the log from a script.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.