Audit and sessions

What is recorded about your operators’ actions, where you and your customers read it, and how to export a per-customer record.

Everything your operators do is recorded: tenant requests, operator changes, sessions opened and ended, baseline revisions saved and applied. The record is written with the action; if it cannot be written, the action does not happen.

​

Where the record lives

Log	What it holds	Who reads it
Your audit log (console, Audit)	Your operators’ actions: requests, operator changes, sessions, baseline revisions	Your operators; Quint
The customer’s audit trail	Every open of their workspace and every action taken inside it under a partner session, under the operator’s name, marked as a partner action	The customer, in their dashboard

The two logs carry the same session from two sides. You see “my operator opened this customer”; the customer sees “a partner operator opened my workspace”.

​

The Audit page

“What operators of this partner did, recorded after commit”. Filter by Window (24h, 7d, 30d, 90d or All recorded) and by Customer. Entries list the time, the action, who did it, which customer, and the recorded details.

Export gives you the per-customer record: “every delegated session and delegate-attributed action for that customer in the range”, watermarked, as CSV or JSON. Choose a customer in the filter first. An export may cover up to eighteen months. Exports stay available for a customer you no longer manage. Exporting needs the Analyst or Admin role.

​

The Sessions page

Sessions lists every read-only session your operators opened, live and ended, with Operator, Customer, Reason, Opens, Created, Expires and Ended by. See Open a customer’s dashboard for what each column means and who can end a session.

​

What is not recorded

• A session’s individual page reads. Each open is recorded; the pages read inside it are not listed one by one.
• Another customer’s data. Your audit log names customers by name and slug only.

​

Next

• Usage and statements
• Your team