2016-07-12 10:49:03 -04:00
|
|
|
# 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 group's project 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, and pull or download the project code.
|
|
|
|
|
|
|
|
|
|
GitLab administrators receive all permissions.
|
|
|
|
|
|
|
|
|
|
To add or import a user, you can follow the [project users and members
|
|
|
|
|
documentation](../workflow/add-user/add-user.md).
|
|
|
|
|
|
|
|
|
|
## Project
|
|
|
|
|
|
|
|
|
|
The following table depicts the various user permission levels in a project.
|
|
|
|
|
|
|
|
|
|
| Action | Guest | Reporter | Developer | Master | Owner |
|
|
|
|
|
|---------------------------------------|---------|------------|-------------|----------|--------|
|
|
|
|
|
| Create new issue | ✓ | ✓ | ✓ | ✓ | ✓ |
|
2017-01-24 06:40:05 -05:00
|
|
|
| Create confidential issue | ✓ | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| View confidential issues | (✓) [^1] | ✓ | ✓ | ✓ | ✓ |
|
2016-07-12 10:49:03 -04:00
|
|
|
| Leave comments | ✓ | ✓ | ✓ | ✓ | ✓ |
|
2017-01-24 06:40:05 -05:00
|
|
|
| See a list of builds | ✓ [^2] | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| See a build log | ✓ [^2] | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| Download and browse build artifacts | ✓ [^2] | ✓ | ✓ | ✓ | ✓ |
|
2016-08-09 18:38:30 -04:00
|
|
|
| View wiki pages | ✓ | ✓ | ✓ | ✓ | ✓ |
|
2016-07-12 10:49:03 -04:00
|
|
|
| Pull project code | | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| Download project | | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| Create code snippets | | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| Manage issue tracker | | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| Manage labels | | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| See a commit status | | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| See a container registry | | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| See environments | | ✓ | ✓ | ✓ | ✓ |
|
2016-10-19 05:54:38 -04:00
|
|
|
| Create new environments | | | ✓ | ✓ | ✓ |
|
2016-12-19 14:18:16 -05:00
|
|
|
| Use environment terminals | | | | ✓ | ✓ |
|
2016-11-17 06:16:13 -05:00
|
|
|
| Stop environments | | | ✓ | ✓ | ✓ |
|
2016-10-04 08:52:08 -04:00
|
|
|
| See a list of merge requests | | ✓ | ✓ | ✓ | ✓ |
|
2016-07-12 11:16:38 -04:00
|
|
|
| Manage/Accept merge requests | | | ✓ | ✓ | ✓ |
|
2016-07-12 10:49:03 -04:00
|
|
|
| Create new merge request | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Create new branches | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Push to non-protected branches | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Force push to non-protected branches | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Remove non-protected branches | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Add tags | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Write a wiki | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Cancel and retry builds | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Create or update commit status | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Update a container registry | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Remove a container registry image | | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Create new milestones | | | | ✓ | ✓ |
|
|
|
|
|
| Add new team members | | | | ✓ | ✓ |
|
|
|
|
|
| Push to protected branches | | | | ✓ | ✓ |
|
|
|
|
|
| Enable/disable branch protection | | | | ✓ | ✓ |
|
|
|
|
|
| Turn on/off protected branch push for devs| | | | ✓ | ✓ |
|
|
|
|
|
| Rewrite/remove Git tags | | | | ✓ | ✓ |
|
|
|
|
|
| Edit project | | | | ✓ | ✓ |
|
|
|
|
|
| Add deploy keys to project | | | | ✓ | ✓ |
|
|
|
|
|
| Configure project hooks | | | | ✓ | ✓ |
|
|
|
|
|
| Manage runners | | | | ✓ | ✓ |
|
|
|
|
|
| Manage build triggers | | | | ✓ | ✓ |
|
|
|
|
|
| Manage variables | | | | ✓ | ✓ |
|
2016-02-19 09:11:26 -05:00
|
|
|
| Manage pages | | | | ✓ | ✓ |
|
|
|
|
|
| Manage pages domains and certificates | | | | ✓ | ✓ |
|
2016-07-12 10:49:03 -04:00
|
|
|
| Switch visibility level | | | | | ✓ |
|
|
|
|
|
| Transfer project to another namespace | | | | | ✓ |
|
|
|
|
|
| Remove project | | | | | ✓ |
|
2017-01-24 06:40:05 -05:00
|
|
|
| Force push to protected branches [^3] | | | | | |
|
|
|
|
|
| Remove protected branches [^3] | | | | | |
|
2016-02-19 09:11:26 -05:00
|
|
|
| Remove pages | | | | | ✓ |
|
2016-07-12 10:49:03 -04:00
|
|
|
|
|
|
|
|
## Group
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
| Action | Guest | Reporter | Developer | Master | Owner |
|
|
|
|
|
|-------------------------|-------|----------|-----------|--------|-------|
|
|
|
|
|
| Browse group | ✓ | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| Edit group | | | | | ✓ |
|
|
|
|
|
| Create project in group | | | | ✓ | ✓ |
|
|
|
|
|
| Manage group members | | | | | ✓ |
|
|
|
|
|
| Remove group | | | | | ✓ |
|
|
|
|
|
|
|
|
|
|
## 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 can only access projects to which they are explicitly granted
|
|
|
|
|
access, thus hiding all other internal or private ones from them. Access can be
|
|
|
|
|
granted by adding the user as member to the project or group.
|
|
|
|
|
|
|
|
|
|
They will, like usual users, receive a role in the project or group with all
|
|
|
|
|
the abilities that are mentioned in the table above. They cannot however create
|
|
|
|
|
groups or projects, and they have the same access as logged out users in all
|
|
|
|
|
other cases.
|
|
|
|
|
|
|
|
|
|
An administrator can flag a user as external [through the API](../api/users.md)
|
|
|
|
|
or by checking the checkbox on the admin panel. As an administrator, navigate
|
|
|
|
|
to **Admin > Users** to create a new user or edit an existing one. There, you
|
|
|
|
|
will find the option to flag the user as external.
|
|
|
|
|
|
|
|
|
|
By default new users are not set as external users. This behavior can be changed
|
|
|
|
|
by an administrator under **Admin > Application Settings**.
|
|
|
|
|
|
2016-08-01 18:31:21 -04:00
|
|
|
## 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
|
|
|
|
|
|
2016-07-12 10:49:03 -04:00
|
|
|
## GitLab CI
|
|
|
|
|
|
|
|
|
|
GitLab CI permissions rely on the role the user has in GitLab. There are four
|
|
|
|
|
permission levels it total:
|
|
|
|
|
|
|
|
|
|
- admin
|
|
|
|
|
- master
|
|
|
|
|
- developer
|
|
|
|
|
- guest/reporter
|
|
|
|
|
|
|
|
|
|
The admin user can perform any action on GitLab CI in scope of the GitLab
|
|
|
|
|
instance and project. In addition, all admins can use the admin interface under
|
|
|
|
|
`/admin/runners`.
|
|
|
|
|
|
|
|
|
|
| Action | Guest, Reporter | Developer | Master | Admin |
|
|
|
|
|
|---------------------------------------|-----------------|-------------|----------|--------|
|
|
|
|
|
| See commits and builds | ✓ | ✓ | ✓ | ✓ |
|
|
|
|
|
| Retry or cancel build | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Remove project | | | ✓ | ✓ |
|
|
|
|
|
| Create project | | | ✓ | ✓ |
|
|
|
|
|
| Change project configuration | | | ✓ | ✓ |
|
|
|
|
|
| Add specific runners | | | ✓ | ✓ |
|
|
|
|
|
| Add shared runners | | | | ✓ |
|
|
|
|
|
| See events in the system | | | | ✓ |
|
|
|
|
|
| Admin interface | | | | ✓ |
|
2016-09-21 10:28:48 -04:00
|
|
|
|
2016-11-30 14:40:53 -05:00
|
|
|
### Builds permissions
|
2016-09-21 10:28:48 -04:00
|
|
|
|
2016-11-30 14:40:53 -05:00
|
|
|
>**Note:**
|
2016-09-22 08:15:43 -04:00
|
|
|
GitLab 8.12 has a completely redesigned build permissions system.
|
2016-09-22 08:04:57 -04:00
|
|
|
Read all about the [new model and its implications][new-mod].
|
2016-09-21 10:28:48 -04:00
|
|
|
|
2016-09-22 08:04:57 -04:00
|
|
|
This table shows granted privileges for builds triggered by specific types of
|
|
|
|
|
users:
|
2016-09-21 10:28:48 -04:00
|
|
|
|
|
|
|
|
| Action | Guest, Reporter | Developer | Master | Admin |
|
|
|
|
|
|---------------------------------------------|-----------------|-------------|----------|--------|
|
|
|
|
|
| Run CI build | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Clone source and LFS from current project | | ✓ | ✓ | ✓ |
|
2016-09-21 10:53:27 -04:00
|
|
|
| Clone source and LFS from public projects | | ✓ | ✓ | ✓ |
|
2017-01-24 06:40:05 -05:00
|
|
|
| Clone source and LFS from internal projects | | ✓ [^4] | ✓ [^4] | ✓ |
|
|
|
|
|
| Clone source and LFS from private projects | | ✓ [^5] | ✓ [^5] | ✓ [^5] |
|
2016-09-21 10:53:27 -04:00
|
|
|
| Push source and LFS | | | | |
|
2016-09-21 10:28:48 -04:00
|
|
|
| Pull container images from current project | | ✓ | ✓ | ✓ |
|
2016-09-21 10:53:27 -04:00
|
|
|
| Pull container images from public projects | | ✓ | ✓ | ✓ |
|
2017-01-24 06:40:05 -05:00
|
|
|
| Pull container images from internal projects| | ✓ [^4] | ✓ [^4] | ✓ |
|
|
|
|
|
| Pull container images from private projects | | ✓ [^5] | ✓ [^5] | ✓ [^5] |
|
2016-09-21 10:28:48 -04:00
|
|
|
| Push container images to current project | | ✓ | ✓ | ✓ |
|
|
|
|
|
| Push container images to other projects | | | | |
|
|
|
|
|
|
2017-01-24 06:40:05 -05:00
|
|
|
[^1]: Guest users can only view the confidential issues they created themselves
|
|
|
|
|
[^2]: If **Public pipelines** is enabled in **Project Settings > CI/CD Pipelines**
|
|
|
|
|
[^3]: Not allowed for Guest, Reporter, Developer, Master, or Owner
|
|
|
|
|
[^4]: Only if user is not external one.
|
|
|
|
|
[^5]: Only if user is a member of the project.
|
2016-09-22 08:04:57 -04:00
|
|
|
[ce-18994]: https://gitlab.com/gitlab-org/gitlab-ce/issues/18994
|
|
|
|
|
[new-mod]: project/new_ci_build_permissions_model.md
|
