1. Docs
  2. Administration
  3. Logs

Logs

Logs is where admins see what happened in the company account: every change, who made it and from where, on which record, and whether it was done, denied or failed.

3 min read Updated CustomersAdmins

In short

On this page you can

  • See every change in your company: created, updated, deleted, archived, ran, signed in and more.
  • Find who changed a test case, a pipeline, a user or a setting, and when.
  • Tell changes made in the app from those made by an AI assistant through MCP or by an API key.
  • See denied attempts: actions someone tried without the rights.
  • Export the filtered list as CSV for an audit.

How to use it

  1. Open Configuration › Logs; it opens on Audit logs.
  2. Narrow the list with From, To, User, Project, Area or the search box.
  3. Click a row to see the request, the result and the sent fields.
  4. Click Export CSV to download what the filters show.

At a glance

Where
Main menu › Configuration › Logs, tab Audit logs.
Who
Admin and Super Admin. Admins see their own company. For the User role the item is greyed out.
Records
Every change: create, update, delete, archive, restore, run, stop, import, export, sign-in and sign-out.
Sources
App, MCP (Claude), API key, Not signed in.
Kept
Records cannot be edited or deleted and are never removed automatically.
Export
CSV of the current filters, up to 50,000 newest records.
Not recorded
Reading, searching and previews; machine traffic such as agent heartbeats and run logs; AI chat questions. Field values of screens that can hold secrets.

Start from your question#

Where Logs fits#

Logs sits beside the order of work. Every step writes to it when someone changes something, so you can trace any change back to a person, a tool and a time.

  1. 1DiscoverActions, App Map changes
  2. 2AnalyzeRequirements
  3. 3AutomateTest cases, steps
  4. 4SchedulePipelines, runs started and stopped
  5. 5ReportExports, comments, defects
  6. 6MaintenanceApprovals and rejections

The same records feed the History of a test case in Automate: “Changes to this test case, its steps and its place in the tree: who, when and from where.”

The building blocks#

Record
One change request: time, user, action, the record it touched, and the result.
Area
The kind of thing changed, for example Test case, Pipeline, Project settings, User, Start page.
Action
What was done: Created, Updated, Deleted, Archived, Restored, Ran, Stopped, Imported, Exported, Signed in, Signed out, Other.
Result
Done, Denied (no permission) or Failed (error).
Source
How the change arrived: the app, an AI assistant through MCP, an API key (CI or scripts), or a request without sign-in.
Sent fields
A short summary of what the request contained. Secrets are shown as ***.

The screen#

  • Refresh (header and list): loads the newest records.
  • Search: matches the record, the user, the request path and the sent fields.
  • Filters: date range, user, project, area, action, result, source. Clear filters resets them.
  • Table: Time, User, Action, Record, Result. Click or press Enter on a row to open its details.
  • Export CSV: downloads what the filters show.

Full reference and procedures: Audit log.

Best practices#

Do

  • Start with a date range and an area; then search.
  • Filter on Denied now and then to spot missing rights or misuse.
  • Filter on MCP (Claude) after an assistant session to review its changes.
  • Export monthly if your auditors need a copy outside SmartestQA.

Don’t

  • Look here for test results: they are in Report.
  • Expect to find who only opened or read a page: reads are not recorded.
  • Share exports widely: they contain names, emails and request paths.

In this section#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai