Named officer · Read-only · Revocable
The inspector gets their own login.
Not a zip file, not a shared mailbox, not a laptop turned round on a desk. A named officer, a read-only account, and a record of exactly what they looked at.
Last updated 18 September 2026
The pain
What this feature fixes.
An inspection becomes an export project.
The officer asks for evidence covering a date range. Somebody spends three days assembling it from four systems, and the officer receives a folder they have to trust was complete.
Shared logins are the usual workaround.
The fastest way to show an auditor the system is to lend them an account. It is also the way to give an external party more access than anyone intended, with no record of who did what.
Nobody can show what was disclosed.
Months later, a question arises about what the officer was shown. The answer lives in an email with an attachment that has since been superseded.
How it works
What you get when you turn this on.
- A named officer gets their own account — no shared credentials
- Read-only by default, scoped to what the inspection actually covers
- Revocable the moment the inspection closes
- Their access is logged, so what was disclosed is itself part of the record
- No licence purchase or seat for the officer's organisation
- Works alongside the evidence pack when a static export is still wanted
[ Inspector Access — screenshot Wave 1.5 ]
With and without
The operating-day difference.
Without Evidix
- Three days assembling a folder of exports
- Lending an auditor a staff login
- No record of what was disclosed
- Access that quietly persists after the audit
With Evidix
- The officer opens the record themselves
- A named, read-only account scoped to the inspection
- Access logged as part of the trail
- Revoked when the inspection closes
Available on
Which plans include this.
Basic
—
Professional
Included
Business
Included
Enterprise
Included
A procurement answer, not a feature.
Give the officer their own way in, and log what they saw.