Audit log

The audit log is the organisation's memory: one searchable list of every action taken in it - by a member in the dashboard, by an agent through an API key, by Argus, or by Vigilator itself (arrival assignments, coverage reassignments, session timeouts, seat-allowance removals). Each entry says who did what, to which thing, and when, and keeps the detail behind it. It is the page to open when a decision needs explaining, a change needs tracing, or a project needs monitoring end to end.

The audit log lives at Audit log in your organisation's sidebar (or press g then u).

Availability

The audit log is a Pro feature. Free organisations see an upgrade prompt in its place - the page's link stays in the sidebar so members know it exists. A Pro trial unlocks it in full; see Billing.

Members also need the auditLog.view permission. The built-in Manager and Developer roles have it, Human does not (a reviewer sees You don't have access to the audit log), and Owner holds everything. Grant it to custom roles under access control. Unlike Analytics, the log is also readable over the API with an API key.

What is recorded

Entries are grouped into categories; the Category and Action filters use the same names.

Entries are written the moment the action happens and are never edited or removed by members - owners included. Every entry names its actor: a member, an API key by its name, Argus, or Vigilator for automatic actions.

Searching

The search box matches an entry's summary, the actor's name, the target's name and the action words. Every word you type must match, as a prefix - refund tanaka finds entries about a refund involving someone called Tanaka, and bill matches billing-agent. There is no phrase or exclusion syntax; narrow with the filters instead.

Filters

The search, the filters and the timeframe are kept in the page URL, so a particular view can be bookmarked or pasted to a colleague. Arriving from a link that points at one thing shows a Target chip above the table; clear it to widen the view again.

Reading an entry

Each row shows when the entry was written (in your time zone, with how long ago), who did it, the action as a coloured badge, a one-line summary, and the thing it was done to. Follow the target to open the interrupt, session, webhook endpoint or settings tab it concerns.

The arrow at the end of a row opens the entry's details: the actor and target, the exact time, the IP address the request came from, and the metadata Vigilator kept - for a decision, the request name and the decision taken; for a role change, the old and new role; for a webhook, the event types it subscribes to.

Loading more

Entries arrive newest first, fifty at a time. Load more appends the next fifty and the count under the table shows how many are on screen. Changing any filter starts again from the newest entry.

Exporting

Export CSV downloads the entries that match the current filters - the most recent 5,000 - with one row per entry and the metadata as JSON in the last column. It needs the auditLog.export permission, which owners and Managers hold by default; the button is hidden from everyone else. Exports are not themselves recorded.

Retention and downgrading

Entries are kept for as long as the organisation exists. If the organisation drops back to the free plan nothing is deleted: the log keeps recording, and the page unlocks again when you upgrade.

API access

Pro organisations can read the same log with an API key - GET /api/audit-log pages through it with the same filters. See the audit log API.

Permissions

Grant them under access control. API keys need no permission of their own: a valid key reads its organisation's log, provided the organisation is on Pro.