Guide

Audit trail and compliance exports

What the audit trail records, how to find an event, the exports, how long entries are kept, and the evidence pack you can hand to an auditor.

3 min read

What is recordedCopy link to this section

Admin › Audit lists every action a Bot took and every one the workspace's rules refused: actions on its computer (allowed, refused, failed or stopped), calls to connected apps and tools, routines and triggers, hand-offs, sign-ins, changes to credentials and rules, and each step of an approval (asked, decided, expired, escalated or delegated). Secrets are masked. Entries are only ever added, and each is chained to the one before it by a hash, so a changed or removed entry shows.

Administrators can open it, and so can members whose role includes View the audit trail; they can filter and export it. Saved filters, the chain check, the evidence pack, the event details and legal holds are for administrators.

Find an eventCopy link to this section

  • Quick views: Everything, Computer actions, Blocked, Did not happen and Nobody watching (started by a routine with no one present).
  • Filter by Event types and by Started by: a person, a routine, a Bot hand-off, a responsibility, a memory source or the workspace itself. Not this turns a filter into an exclusion.
  • Search across the target, tool, reason, rule and person. Each row has Copy JSON; an administrator can open the event to see everything recorded, related events and its place in the hash chain, and copy a link to it.
  • Administrators can keep up to 50 Saved filters each, for the views they open often.

ExportCopy link to this section

Download CSV and JSON export the whole filtered trail, not only the page on screen, up to 100,000 rows; narrow the filters or the dates for a larger range. Verify chain checks the hash chain over the dates in view.

The evidence packCopy link to this section

Evidence pack downloads one zip of the current filtered view for an auditor, with a manifest giving the SHA-256 and size of every file:

FileContents
audit-trail.csvThe filtered trail.
boundaries/policy.json, boundaries/versions.jsonThe boundary rules in force and their history.
access-review.csvEach person's role, last sign-in, Bots, keys, connected accounts and approval rules.
retention.jsonThe retention settings.
chain-verification.jsonThe result of the chain check.
manifest.jsonWhen and by whom the pack was made, the filters used, each file's hash and size, and the chain head.

Admin › Compliance overview adds reports drawn from the trail, privileged activity and configuration changes, each as a CSV for up to a year, and a signed export of the trail.

How long entries are keptCopy link to this section

By default the audit trail is kept for good. Under Admin › Enterprise controls › Retention an administrator can set it to anything from 30 to 3,650 days; older entries are removed once an hour. An entry under a Legal hold, placed from the event's details, is never removed by retention until the hold is released.

Last updated