Audit log
The audit log lists every change in your company, newest first. This page shows how to find a change, what a record tells you, and what is never recorded.
In short
On this page you can
- Find a change by date, user, project, area, action, result or source.
- Open a record to see the request, its status, duration and the fields that were sent.
- Review what an AI assistant changed through MCP.
- List denied and failed attempts.
- Export up to 50,000 records as CSV.
How to use it
- Open Configuration › Logs › Audit logs.
- Set From and To, then Area or User.
- Type a name or path in the search box; the list updates as you type.
- Click the row to read its details.
- Click Export CSV to keep a copy.
Filters and search#
| Filter | What it narrows |
|---|---|
| Search (“Search record, user, path or fields”) | Record names, user names and emails, request paths and sent fields. Applies shortly after you stop typing. |
| From · To | Date range. |
| User | People who have records. |
| Project | Projects that have records. |
| Area | The kind of record, for example Test case, Pipeline, Action, Project settings, User. |
| Action | Created, Updated, Deleted, Archived, Restored, Ran, Stopped, Imported, Exported, Signed in, Signed out, Other. |
| Result | Done, Denied, Failed. |
| Source | App, MCP (Claude), API key, Not signed in. |
Each list starts with All. Clear filters resets everything. Show 25, 50 or 100 records per page; the default is 50.
Find who changed something#
Set the time window
Pick From and To around the moment it changed.
Pick the area and action
For example Area = Test case and Action = Deleted.
Search the name
Type part of the test case name.
The row shows who did it, when, from which source, and whether it went through.
For one test case, its History in Automate shows the same records without filtering.
Review an AI assistant’s changes#
Set Source = MCP (Claude) and the date of the session. Each row is one change the assistant applied after your approval, under your name. Filter Result = Denied to see what it tried without the rights.
See attempts without permission#
Set Result = Denied. Each row is a request that was refused because of the person’s role or company, for example a User trying to delete a module. Failed rows are requests that ended with an error.
What a record shows#
| Column | Meaning |
|---|---|
| Time | Local date and time, to the minute. |
| User | Who made the request (hover for the email), with the source below: App, MCP (Claude), API key or Not signed in. |
| Action | The action word, with the area below it, for example Updated / Project settings. |
| Record | The name of the record, or #id when it has no name, with its project below. |
| Result | Done (green), Denied (amber) or Failed (red), always with the word. |
Click the row for its details:
| Detail | Meaning |
|---|---|
| Request | HTTP method and path, for example PUT /api/project-preferences/project/42/batch. |
| Operation | The server function that handled it. |
| Status | HTTP status and duration, for example 200 · 35 ms. Denied requests usually show 403. |
| Message | The error message, for failed or denied requests. |
| E-mail · Client · Request ID | The user’s email, the browser or tool, and an ID to quote to support. |
| Sent fields | A summary of the request: at most 30 top-level fields, texts cut at 200 characters, lists shown as a count, nested objects left out. Field names that look secret (password, token, API key, credential…) show ***. “Not recorded for this action (no fields, or the screen may hold secrets).” when nothing is stored. |
What is and is not recorded#
Recorded
- Every request that changes something: creating, updating, deleting, archiving, restoring, running, stopping, importing, exporting.
- Sign-in and sign-out.
- Denied and failed attempts, not only successful ones.
- Changes from the app, from MCP and from API keys alike.
Not recorded
- Opening, reading, searching, previews, calculations and connection tests.
- Machine traffic: agent heartbeats, run logs written by the runner, device telemetry.
- AI chat and AI questions, notifications marked as read, tours shown.
- Field values of screens that can hold secrets: sign-in, users, project members, data sources and database connections, AI configuration, agents and runners, mobile configuration, licence and payments, global parameters, integrations and Active Directory. The record itself is kept.
How the action word is chosen#
From the name of the server function, then from the HTTP method:
login… → Signed in logout… → Signed out
…restore… → Restored archive… → Archived
delete / remove / purge… → Deleted import… / export… → Imported / Exported
stop / abort / cancel… → Stopped run / execute / start / trigger… → Ran
create / add / upload / clone / duplicate / generate… → Created
update / edit / rename / set / move / approve / reject / assign / save… → Updated
otherwise: PUT or PATCH → Updated · DELETE → Deleted · else → OtherExample: approving an auto-heal repair in Maintenance is recorded as Updated; starting a pipeline as Ran; cancelling it as Stopped.
Export as CSV#
Set the filters
The export contains exactly what the filters and the search show.
Click Export CSV
The button is greyed out while the list is empty.
A CSV file downloads with the newest records first, up to 50,000.
For more than 50,000 records, export in several date ranges. A failure shows “Export failed.”
If something goes wrong#
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai