Audit trail
Every change to your agents, skills, knowledge bases and settings is recorded with who made it, when, and what changed — from the console, the API and MCP alike. Readable in the console, exportable as CSV, kept for two years, and not deletable by anyone.
Sooner or later someone asks a question you cannot answer from memory: who changed the agent's instructions before it started saying that? Or an auditor asks a version of it in writing. The Audit trail in your console answers both.
It records every change to the things you configure — agents, share links, skills, knowledge bases and their documents, storylines, MCP servers, page contexts, products, scheduled tasks, spaces and your account settings. For each one it keeps four things:
| What is recorded | What it holds |
|---|---|
| Who | The console user's email, or the name of the API key. The name is stored with the entry, so it stays readable after the key is deleted. |
| When | Server timestamp, to the second. |
| What | The object, by the name you gave it — not only an internal ID. |
| Before → after | The fields that actually changed, with their old and new values. |
It does not depend on where the change came from
This is the part worth understanding, because it is what makes the record trustworthy.
The trail is written at the database layer, not by each feature separately. Anything that changes your data passes through it — so a change made by clicking in the console, by a script calling the REST API, and by a coding agent using MCP are all recorded the same way, without any of them having to remember to. A new feature is covered the day it ships.
Each entry also records how the request arrived — console, rest, mcp or script. Those
are the same API key in every case, so without that column they would be indistinguishable, and
"who did this" usually starts with narrowing that down.
Only the fields that changed
An entry shows a diff, not a snapshot. Changing one setting on an agent records that one setting, with its old and new value — you are not handed the whole object to compare yourself.
Prompt text is kept in full. An agent's persona, task and a skill's instructions are recorded verbatim, both versions, however long they are. Those are exactly what you need when the question is "why did it answer that way last week", and a truncated copy answers nothing.
Credentials are never recorded — not the value, not the hash. Nor are the numeric vectors behind knowledge retrieval, which are neither readable nor evidence of anything. API keys have their own entries (issued, revoked, deleted), so nothing is lost by keeping the key material out.
Reading and exporting it
Console → Audit trail. Filter by object type or search by name — what happened to the agent
called support is usually the real question, and it does not require looking up an ID first.
Expand a row to see the changed fields.
Export CSV downloads the current filter, with before and after as JSON so the file stays
machine-readable. In a compliance review, "let me show you" and "here is a copy" are different
requests, and a screenshot is not a copy.
What you cannot do
You cannot edit or delete entries. Neither can we, from the product. There is no button, and no API call. A record the subject can alter is not evidence, and the whole point of this page is that it is.
Entries are kept for two years, then removed automatically. If your obligations require longer, export on a schedule — the CSV endpoint is part of the REST API and takes the same filters as the page.
When support looks at your account
If you ask our support team to open your account, what they see is this same trail, from the same table — not a separate internal log. Their actions in your account appear in it too, attributed to them.
Related
- Workspace ID, API key, tool token & console — where the key names in the who column come from.
- Team members — why colleagues should have their own sign-in rather than sharing one: the trail names a person only if the person has an account.
- Private by design — isolation and encryption, the other half of what an auditor will ask about.