What the staff audit trail covers
Audit Logs, in the Available Apps panel, opens the platform audit trail. This page is the reference for its scope, its services and its event names.
- Access to Audit Logs in the staff console.
- A staff sign-in. Audit logs are for staff only; a tenant session is refused.
If an area or a button is missing, your staff role does not include it. Ask a platform administrator to extend your access.
Whose events you see
One tenant and one service at a time, because the trail is kept per tenant and per source service. Until you choose both, the page reads Choose a tenant to begin and nothing is fetched.
A staff session may read any tenant's trail, but only the one chosen in Select tenant: there is no cross-tenant view. The page never refreshes by itself, because every search and every event you open is itself recorded against the tenant you looked at.
Billing changes made in the staff console have their own trail, under Billing then Audit. See Invoices, reconciliation and the billing audit.
The services
Select service lists each service by a readable name with its internal name beneath. The page starts on IntELIEDocs.
| Service | Reports |
|---|---|
| IntELIEDocs, Documents, Knowledge Base, Security, Audit (its own reads) | Chained producers: every event is hash-linked, so a gap in the Chain position numbers points to tampering. The API key events are on Security. |
| Workflow engine, Text extraction (Lens), Classification, Field extraction, Document normalization and the Knowledge Base ingestion worker | The processing pipeline. They publish directly, with no chain proof, so a gap means telemetry was lost, not that the work did not happen. |
| Voice IntELIEgence, IntELIEKonnect | Their own module's events. Voice includes voice identification. These also show without chain proof. |
The chip in the Trail bar tells you which kind you picked: chained producer · events hash-linked or pipeline worker · no chain proof.
Event names
Every event shows a readable sentence with its raw name beneath. Matching is from the start of the name, so a family prefix returns the whole group. Open the chevron under Event type in Filters for the full list.
| Prefix | What it returns |
|---|---|
document_ | Every document journey event |
file_ | Every file lifecycle event |
smart_extract_ | Every extractor event |
smart_class_ | Every classifier event |
smart_queue_ | Every queue event |
auth.api_key. | Every API key event, on the Security trail |
The pipeline workers share one set instead, from task_started (Processing step started) to
task_failed (Processing step failed); which work a row describes comes from the service you
chose and the stage row under Details. The set is not closed: a name the console does not
know is still shown, spelled out from the name itself.
Next
- Searching the staff audit trail - choosing the trail and filtering it.
- Reading one audit event - the details panel.