Audit Log
What is it?
The audit log is the complete record of every change in your organization: who changed what, and when. Every mutation (project created, station edited, member invited, report requested, …) creates an entry. You'll find it under Quality → Audit log and can export it as CSV.
The stored codes stay technical (for evidence and analysis). In the list you see the same entries in plain language: the action as a sentence, the object name instead of an internal ID, and where available the change itself (for example old and new status).
How to use it
- Viewing it: Quality → Audit log. The list is chronological (newest first) and shows time, actor, action, affected object, and details. Names are clickable while the object still exists.
- Exporting: The CSV export gives you the entries for archiving, proof, or external analysis. The file includes both the readable labels and the technical codes plus raw JSON.
The page shows 25 entries per page and provides access to the full history. The export contains up to 10,000 of the most recent entries and displays a notice after downloading when additional entries exist.
Actor types
Every entry records who acted:
- User — a logged-in human triggered the change.
- Agent — an AI assistant or an API token acted. If the entry says “on behalf of …”, that is the person the action is attributed to.
- System — an automatic background process (e.g., a scheduled reminder or a job) with no direct human trigger.
Common issues
- "I see a change but no one who caused it." If the actor is System, it was an automatic process (job, reminder), not a user action. That's normal.
- "Why does an agent show up in the log?" If you use the AI support assistant or the REST API with an organization token, those actions are logged as Agent — that's exactly what the distinction is for.
- "An entry is missing." The audit log records data changes, not plain reads (opening a list doesn't create an entry). Only mutations are logged.
- "I see a code instead of a sentence." Very old or very new actions
without a translation appear as a technical name. The entry is still valid;
the CSV has the same code in the
actioncolumn. - "The object name is missing or the link doesn't work." The object was deleted, or the entry never stored a name. The type and action remain.
- Entries are only visible for your own organization. A log entry from another organization is technically unreachable (tenant isolation), not just hidden.