

The tabs
The screen has up to three tabs, each offered only to people who may read it. With only one to offer, there is no row of tabs at all.
The tab you are on is part of the page’s address, so a link or a bookmark opens the same tab. A link
to a tab you may not see opens the first one you may.
What is recorded
The product writes an event whenever a record is created, changed or deleted, and for actions such as signing in. Each event records:
Nobody can edit or delete an audit event, from this screen or anywhere else. The trail is kept in
monthly sections; the stat strip says how many it holds.
The stat strip
Narrowing the trail
Every search is bounded by its dates — the dates decide how much of the trail is read, so narrow them first for a fast answer.
Clear filters removes them all. On a phone the filters are behind Filters, closed with
Done.
The overview
While only the dates are set, two panels summarise the period: Busiest record types and Busiest people, each with a count. They cover the dates only, so they are hidden as soon as you narrow anything else, and a note says so (“Narrowed — the totals above cover the dates only”). If nothing in the period was done by a person, the people panel says every event was written by the product itself. If you may open User activity, each person under Busiest people has a chart icon, What they did, by module, which opens what that person created and changed on the User activity tab.What happened
The list of events, newest first, with a count. Three buttons in the section’s heading choose how the same events are laid out, and the screen remembers your choice on this device:
The three views show exactly the same events: the dates, filters, the 100-at-a-time loading and the
export mean the same in each. That is also why the columns do not sort — a sort would order only the
events loaded so far. In both tables, a person’s name narrows the list to that person, a record type
narrows it to that kind of record, the funnel beside it narrows it to that one record, and the arrow
opens the record.
In the feed, each event shows its summary, who did it, when, its action and record type, and three
links:


Exporting
Export downloads the trail for the period as a CSV file, with the columns When, Record type, Record, Action, Who, From, Fields changed, What happened and Reason. An export carries the dates, the record type and the person — nothing else. If you have set an action, a source, a field or a text search, a note above the list says the file would be wider than the list on screen. An export stops at 10,000 events; if it reaches that, a warning asks you to narrow the dates and take it again. To send the trail to your security team’s SIEM continuously, see security events.Verification scans
Verification scans lists every label somebody read on a verification round, across every round, newest first — on the web or on a handset. A scan changes no record, so it never appears on the Changes tab; this is where the evidence that an asset was physically seen is read. Nothing on this tab records anything. The stat strip counts the scans, the assets and the people in what is shown, and how many scans did not match the asset they were recorded against.
Clear filters puts them back.
The list loads 200 scans at a time; Show 200 more loads the next. When nothing was scanned the
screen says Nothing scanned in these dates. Export downloads what is shown as a CSV file, with
the asset number and name in separate columns and Matched the asset as Yes or No; it needs
Audit · export.
Who can use this screen
Somebody without Audit · view who opens the address is told that reading the whole trail needs
the audit permission; the history tab on a record they can already see is unaffected.

