Skip to content

Audit log

Your workspace keeps an audit log. It is under Settings → Workspace → Audit log, visible to workspace owners (an owner can open it to every member).

Kind Examples
Changes A workflow renamed, a schedule paused, a connection’s credential replaced (the log says the credential changed, never what it changed to), a member added, a version activated — with who did it, when, and each field before and after. When an agent made the change through a tool, the entry links to the run that did it. When a learning loop made it (a new version promoted from its evaluations, for example), the entry names the loop and the records it learned from.
Activity Sign-ins and new devices, failed sign-ins, exports and downloads, runs started or cancelled, a webhook or embed token used, consent granted or withdrawn, a data-erasure request, a vault document opened — and every time a platform operator accessed your workspace, with the reason they gave.

Reading the audit log is not itself recorded; exporting it is.

Each thing in your workspace also has its own History on its page — a workflow’s settings, a schedule, a connection, a template — showing the same entries for that one thing, and where its trail begins.

Platform operators can read a workspace’s records for support. Every such read is written to your audit log, by name and with the reason, and the workspace owners are notified. The same notification is sent when someone exports your audit log, when training consent is withdrawn, and when a data-erasure request is made.

Export on the audit log downloads everything the log holds for a date range. Three formats: a line-per-record JSON file (the complete form), CSV, or an OpenTelemetry-shaped file for your own observability tools. The export is recorded in the log and the owners are notified.

Under Settings → Workspace → Decision records:

Setting What it does
Keep decision records for How many days a run’s decision records are kept. Your organisation sets the default and the maximum.
Audit floor Changes and activity are always kept for at least the number of days your organisation requires, whatever the setting above. Feedback is never removed.
Legal hold While on, nothing in your workspace’s records is removed. Your organisation can place a hold on every workspace.
Who may read the audit log Owners, or all members.

By default, nothing from your workspace is used to train or improve models. Where your organisation allows it, a workspace owner can turn on Allow this workspace’s records to be used for training. While it is on, decision records and feedback from this workspace may be used outside the workspace for that purpose. The setting is checked at the moment of use — turning it off also stops any later use. Nothing inside the workspace (your own trail, your own evals, your own audit log) needs it.

When a person’s login is deleted, their name is removed from the records that named them; the workspace’s records of what happened stay. If content about a person has to be removed from a run — a visitor’s words in a conversation — ask your platform operator: the run’s conversation is replaced with a marker, and the run still shows that it happened and what it cost.