Auditor portal
Audit tokens give an external auditor a read-only link (/audit/<token>) to frameworks, assessments, risks, policies, tests and incidents. They are created under New Audit Token, with a description, partner email (optional) and validity in days (required, 90 at most); Revoke disables the link immediately.
When you create the token you choose the entity the auditor can access: the auditor sees only that entity's data, never the other entities' (important for a consultancy, where each client is an entity). The All entities option gives access to everything, must be chosen explicitly and only shows for people who see all entities. On a single-entity token, the sections that are not tied to an entity (continuity tests, audit findings, CAPA and the statement of applicability) appear empty; only all-entities links show them. Every time the link is opened it is recorded, with the date, IP address, browser and page. Links created before this version, in an organisation with several entities, stop opening: create them again, choosing the entity. In an organisation with a single entity they keep working.
There are four additional sections you can add to each token, under Additional sections in the form. They are off by default (old tokens do not have them) and are read-only:
| Section | What the auditor sees |
|---|---|
| Evidence (metadata) | List of evidence without the files. Evidence with a high classification never appears |
| Audit findings | The findings recorded |
| CAPA | Corrective and preventive actions |
| Statement of Applicability | The SoA, with the Annex A controls decided and the justifications |
The portal shows only data from the token's organisation, with no user identifiers or emails, no file references and no text extracted from documents. Blank values appear as a hyphen. Turn on only the sections the auditor needs.
EterShield: vCISO Platform · Eter Growth · geral@etergrowth.com