Auditor users

{{< details >}}

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

Auditor users have read-only access to all groups, projects, and other resources in the instance.

Auditor users:

• Have read-only access to all groups and projects.
  • Due to a known issue, users must have the Reporter, Developer, Maintainer, or Owner role to perform read-only tasks.
• Can have additional permissions to groups and projects based on their assigned role.
• Can create groups, projects, or snippets in their personal namespace.
• Cannot view the Admin area or perform any administration actions.
• Cannot access group or projects settings.
• Cannot view job logs when debug logging is enabled.
• Cannot access areas designed for editing, including the pipeline editor.

Auditor users are sometimes used in situations where:

• An organization needs to test security policy compliance across an entire GitLab instance. An auditor user can do this without being added to every project or given administrator access.
• A specific user needs to view a large number of projects in the GitLab instance. Instead of manually adding the user to every project, you can create an auditor user that can access every project automatically.

[!note] An auditor user counts as a billable user and consumes a license seat.

Create an auditor user

Prerequisites:

• Administrator access.

To create a new auditor user:

1. In the upper-right corner, select Admin.
2. Select Overview > Users.
3. Select New user.
4. In the Account section, enter the required account information.
5. For User type, select Auditor.
6. Select Create user.

You can also create auditor users with:

• SAML groups.
• The users API.