Read-only by construction
The auditor role has no write permission anywhere in the role matrix.
FOR AUDIT AND ASSURANCE
Read-only evidence you can sample and cite.
Every generated artefact names its source, generation time, scope, and staleness. Enterprise provides a dedicated read-only auditor role.
Context
The situation
You need to test a control, sample its evidence, and cite the sample — without being given a login that can change anything.
Every generated artefact names its source, generation time, scope, and staleness. Enterprise provides a dedicated read-only auditor role. Generated evidence is never itself an authority.
On this page
What you get from this
Separate audit history
Audit history is stored separately from telemetry and is append-only.
Personal and Pro are not the fit
Personal has no history. Team has shared audit history without a dedicated auditor role.
Collection boundary
The boundary
We observe here
Precyz does not assert that a control passed. It shows you the record and tells you where the record came from.
We never collect here
Communication content, URLs, paths, query strings, DNS names beyond the registrable domain, headers, cookies, tokens, files, screenshots, form data, keystrokes, usernames, email addresses, hardware serial numbers, or precise location.
Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.
Availability across plans
Personal
Not included
Pro
Reports, no dedicated auditor role
Team
90-day audit history
Enterprise
Quoted audit history and auditor role