> For the complete documentation index, see [llms.txt](https://docs.cerrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cerrix.com/best-practices-and-guides/access-for-external-auditors.md).

# Access for External Auditors

When an external audit is coming up, CERRIX offers two supported ways to give auditors access to the data in scope. Which one fits best depends on how your auditors want to work: do they want to log in and browse CERRIX on screen, or pull data into their own audit tooling?

## Option 1: Named viewer accounts

If your auditors want to log in and review data in CERRIX itself, create a personal account for each auditor and grant the minimum rights needed. For an external audit, that is normally read-only **Viewer** roles on the modules in scope, for example:

* **Risk — Viewer**
* **Controls — Viewer** (add **Control Reviewer** only if the auditor needs to review or sign off test results)
* **Events/Incidents — Viewer**
* **Third Party — Viewer**

Each Viewer role comes in two scopes: **Unrestricted** (all organizations) or **Restricted** (a single organization). For an external audit, choose **Restricted**, scoped to the organization(s) covered by the audit, unless the auditors genuinely need to see the full environment.

Give every auditor their own account with a personal email address. Each email address is linked to one account, and accounts use personal (not generic or shared-mailbox) email addresses, so notifications reach the right person.

### Signing in from the auditor's own device

CERRIX runs in the browser, so external auditors can work from their own laptop — no company-managed device is required on the CERRIX side. What decides this in practice is how the account signs in:

* **Standard CERRIX login (username/password)** works from any device, including the auditor's own laptop. This is the usual setup for external parties, since they sit outside your identity provider.
* **Login via your own SSO/identity provider** follows your organization's identity policies, which may include device or network restrictions that block an unmanaged external laptop.

Set external auditors up with a standard CERRIX login rather than routing them through your SSO. If your CERRIX environment is configured for SSO-only sign-in, check with your IT team whether standard logins are allowed alongside it.

## Option 2: External Connections (Third Party Assurance)

If your auditors prefer to pull risks, controls, test results, and improvement actions straight into their own audit tooling instead of clicking through the UI, use CERRIX **External Connections**. This mechanism is purpose-built for third-party assurance: it is read-only by design, time-boxed, and IP-restricted, and it avoids creating and managing separate login accounts.

See [External Connections](https://docs.cerrix.com/cerrix-functionalities/admin-settings/external-connections.md) for the step-by-step setup.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cerrix.com/best-practices-and-guides/access-for-external-auditors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
