• Principles behind permissions
• Instance-wide user permissions
• Project members permissions
• Project features permissions
  • Wiki and issues
  • 保護ブランチ
  • Value Stream Analytics permissions
  • Issue Board permissions
  • File Locking permissions
  • Confidential Issues permissions
• Group members permissions
  • Subgroup permissions
• External users
  • Setting new users to external
• Free Guest users
• Auditor users
• Project features
• GitLab CI/CD permissions
  • Job permissions
  • New CI job permissions model
• Running pipelines on protected branches
• LDAP users permissions
• プロジェクトのエイリアス

権限

Users have different abilities depending on the access level they have in a particular group or project. If a user is both in a project’s group and the project itself, the highest permission level is used.

On public and internal projects the Guest role is not enforced. All users will be able to:

• Create issues.
• Leave comments.
• Clone or download the project code.

When a member leaves a team’s project, all the assigned Issues and Merge Requests will be unassigned automatically.

GitLab administrators receive all permissions.

To add or import a user, you can follow the project members documentation.

Principles behind permissions

See our product handbook on permissions.

Instance-wide user permissions

By default, users can create top-level groups and change their usernames. A GitLab administrator can configure the GitLab instance to modify this behavior.

Project members permissions

While Maintainer is the highest project-level role, some actions can only be performed by a personal namespace or group owner, or an instance admin, who receives all permissions. For more information, see projects members documentation.

The following table depicts the various user permission levels in a project.

* Owner permission is only available at the group or personal namespace level (and for instance admins) and is inherited by its projects.

1. Guest users are able to perform this action on public and internal projects, but not private projects.
2. Guest users can only view the confidential issues they created themselves.
3. If Public pipelines is enabled in Project Settings > CI/CD.
4. Not allowed for Guest, Reporter, Developer, Maintainer, or Owner. See Protected Branches.
5. If the branch is protected, this depends on the access Developers and Maintainers are given.
6. Guest users can access GitLab Releases for downloading assets but are not allowed to download the source code nor see repository information like tags and commits.
7. Actions are limited only to records owned (referenced) by user.
8. When Share Group Lock is enabled the project can’t be shared with other groups. It does not affect group with group sharing.
9. For information on eligible approvers for merge requests, see Eligible approvers.

Project features permissions

Wiki and issues

Project features like wiki and issues can be hidden from users depending on which visibility level you select on project settings.

• Disabled: disabled for everyone
• Only team members: only team members will see even if your project is public or internal
• Everyone with access: everyone can see depending on your project visibility level
• Everyone: enabled for everyone (only available for GitLab Pages)

保護ブランチ

Additional restrictions can be applied on a per-branch basis with protected branches. Additionally, you can customize permissions to allow or prevent project Maintainers and Developers from pushing to a protected branch. Read through the documentation on Allowed to Merge and Allowed to Push settings to learn more.

Value Stream Analytics permissions

Find the current permissions on the Value Stream Analytics dashboard, as described in related documentation.

Issue Board permissions

Developers and users with higher permission level can use all the functionality of the Issue Board, that is create/delete lists and drag issues around. Read through the documentation on Issue Boards permissions to learn more.

File Locking permissions

The user that locks a file or directory is the only one that can edit and push their changes back to the repository where the locked objects are located.

Read through the documentation on permissions for File Locking to learn more.

Confidential Issues permissions

Confidential issues can be accessed by reporters and higher permission levels, as well as by guest users that create a confidential issue. To learn more, read through the documentation on permissions and access to confidential issues.

Group members permissions

Any user can remove themselves from a group, unless they are the last Owner of the group. The following table depicts the various user permission levels in a group.

1. Groups can be set to allow either Owners or Owners and Maintainers to create subgroups
2. Introduced in GitLab 12.2.
3. Default project creation role can be changed at:
   • The instance level.
   • The group level.
4. Does not apply to subgroups.

Subgroup permissions

When you add a member to a subgroup, they inherit the membership and permission level from the parent group(s). This model allows access to nested groups if you have membership in one of its parents.

To learn more, read through the documentation on subgroups memberships.

External users

In cases where it is desired that a user has access only to some internal or private projects, there is the option of creating External Users. This feature may be useful when for example a contractor is working on a given project and should only have access to that project.

External users:

• Cannot create groups, projects, or personal snippets.
• Can only access public projects and projects to which they are explicitly granted access, thus hiding all other internal or private ones from them (like being logged out).

Access can be granted by adding the user as member to the project or group. Like usual users, they will receive a role in the project or group with all the abilities that are mentioned in the permissions table above. For example, if an external user is added as Guest, and your project is private, they will not have access to the code; you would need to grant the external user access at the Reporter level or above if you want them to have access to the code. You should always take into account the project’s visibility and permissions settings as well as the permission level of the user.

An administrator can flag a user as external by either of the following methods:

• Either through the API.
• Or by navigating to the Admin Area > Overview > Users to create a new user or edit an existing one. There, you will find the option to flag the user as external.

Setting new users to external

By default, new users are not set as external users. This behavior can be changed by an administrator on the Admin Area > Settings > General page, under Account and limit.

If you change the default behavior of creating new users as external, you will have the option to narrow it down by defining a set of internal users. The Internal users field allows specifying an email address regex pattern to identify default internal users. New users whose email address matches the regex pattern will be set to internal by default rather than an external collaborator.

The regex pattern format is Ruby, but it needs to be convertible to JavaScript, and the ignore case flag will be set (/regex pattern/i). Here are some examples:

• Use \.internal@domain\.com$ to mark email addresses ending with .internal@domain.com as internal.
• Use ^(?:(?!\.ext@domain\.com).)*$\r? to mark users with email addresses NOT including .ext@domain.com as internal.

Free Guest users

When a user is given Guest permissions on a project, group, or both, and holds no higher permission level on any other project or group on the GitLab instance, the user is considered a guest user by GitLab and will not consume a license seat. There is no other specific “guest” designation for newly created users.

If the user is assigned a higher role on any projects or groups, the user will take a license seat. If a user creates a project, the user becomes a Maintainer on the project, resulting in the use of a license seat. Also, note that if your project is internal or private, Guest users will have all the abilities that are mentioned in the permissions table above (they will not be able to browse the project’s repository for example).

Auditor users

Auditor users are given read-only access to all projects, groups, and other resources on the GitLab instance.

An Auditor user should be able to access all projects and groups of a GitLab instance with the permissions described on the documentation on auditor users permissions.

Read more about Auditor users.

Project features

Project features like wiki and issues can be hidden from users depending on which visibility level you select on project settings.

• Disabled: disabled for everyone
• Only team members: only team members will see even if your project is public or internal
• Everyone with access: everyone can see depending on your project visibility level
• Everyone: enabled for everyone (only available for GitLab Pages)

GitLab CI/CD permissions

GitLab CI/CD permissions rely on the role the user has in GitLab. There are four permission levels in total:

• admin
• maintainer
• developer
• guest/reporter

The admin user can perform any action on GitLab CI/CD in scope of the GitLab instance and project. In addition, all admins can use the admin interface under /admin/runners.

1. Only if the job was:
   • Triggered by the user
   • Since GitLab 13.0, not run for a protected branch

Job permissions

Note: GitLab 8.12 has a completely redesigned job permissions system. Read all about the new model and its implications.

This table shows granted privileges for jobs triggered by specific types of users:

1. Only if the user is not an external one
2. Only if the user is a member of the project

New CI job permissions model

GitLab 8.12 has a completely redesigned job permissions system. To learn more, read through the documentation on the new CI/CD permissions model.

Running pipelines on protected branches

The permission to merge or push to protected branches is used to define if a user can run CI/CD pipelines and execute actions on jobs that are related to those branches.

See Security on protected branches for details about the pipelines security model.

LDAP users permissions

Since GitLab 8.15, LDAP user permissions can now be manually overridden by an admin user. Read through the documentation on LDAP users permissions to learn more.

プロジェクトのエイリアス

Project aliases can only be read, created and deleted by a GitLab administrator. Read through the documentation on Project aliases to learn more.