permissions.md 7.17 KB
Newer Older
Marin Jankovski's avatar
Marin Jankovski committed
1 2
# Permissions

3
Users have different abilities depending on the access level they have in a particular group or project.
4

5
If a user is both in a project group and in the project itself, the highest permission level is used.
6

7 8
If a user is a GitLab administrator they receive all permissions.

9
On public and internal projects the Guest role is not enforced.
10
All users will be able to create issues, leave comments, and pull or download the project code.
11

Karen's avatar
Karen committed
12
To add or import a user, you can follow the [project users and members
13
documentation](../workflow/add-user/add-user.md).
14

15 16 17 18 19 20
## Project

| Action                                | Guest   | Reporter   | Developer   | Master   | Owner  |
|---------------------------------------|---------|------------|-------------|----------|--------|
| Create new issue                      | ✓       | ✓          | ✓           | ✓        | ✓      |
| Leave comments                        | ✓       | ✓          | ✓           | ✓        | ✓      |
21 22 23
| See a list of builds                  | ✓ [^1]  | ✓          | ✓           | ✓        | ✓      |
| See a build log                       | ✓ [^1]  | ✓          | ✓           | ✓        | ✓      |
| Download and browse build artifacts   | ✓ [^1]  | ✓          | ✓           | ✓        | ✓      |
24 25
| Pull project code                     |         | ✓          | ✓           | ✓        | ✓      |
| Download project                      |         | ✓          | ✓           | ✓        | ✓      |
26
| Create code snippets                  |         | ✓          | ✓           | ✓        | ✓      |
27 28
| Manage issue tracker                  |         | ✓          | ✓           | ✓        | ✓      |
| Manage labels                         |         | ✓          | ✓           | ✓        | ✓      |
29
| See a commit status                   |         | ✓          | ✓           | ✓        | ✓      |
30
| See a container registry              |         | ✓          | ✓           | ✓        | ✓      |
31
| See environments                      |         | ✓          | ✓           | ✓        | ✓      |
32
| Manage merge requests                 |         |            | ✓           | ✓        | ✓      |
33 34 35
| Create new merge request              |         |            | ✓           | ✓        | ✓      |
| Create new branches                   |         |            | ✓           | ✓        | ✓      |
| Push to non-protected branches        |         |            | ✓           | ✓        | ✓      |
36
| Force push to non-protected branches  |         |            | ✓           | ✓        | ✓      |
37 38 39
| Remove non-protected branches         |         |            | ✓           | ✓        | ✓      |
| Add tags                              |         |            | ✓           | ✓        | ✓      |
| Write a wiki                          |         |            | ✓           | ✓        | ✓      |
40
| Cancel and retry builds               |         |            | ✓           | ✓        | ✓      |
41
| Create or update commit status        |         |            | ✓           | ✓        | ✓      |
42
| Update a container registry           |         |            | ✓           | ✓        | ✓      |
Kamil Trzciński's avatar
Kamil Trzciński committed
43
| Remove a container registry image     |         |            | ✓           | ✓        | ✓      |
44
| Create new environments               |         |            | ✓           | ✓        | ✓      |
45
| Create new milestones                 |         |            |             | ✓        | ✓      |
46 47
| Add new team members                  |         |            |             | ✓        | ✓      |
| Push to protected branches            |         |            |             | ✓        | ✓      |
Ben Bodenmiller's avatar
Ben Bodenmiller committed
48
| Enable/disable branch protection      |         |            |             | ✓        | ✓      |
49
| Turn on/off prot. branch push for devs|         |            |             | ✓        | ✓      |
50 51
| Rewrite/remove git tags               |         |            |             | ✓        | ✓      |
| Edit project                          |         |            |             | ✓        | ✓      |
Ben Bodenmiller's avatar
Ben Bodenmiller committed
52 53
| Add deploy keys to project            |         |            |             | ✓        | ✓      |
| Configure project hooks               |         |            |             | ✓        | ✓      |
54 55 56
| Manage runners                        |         |            |             | ✓        | ✓      |
| Manage build triggers                 |         |            |             | ✓        | ✓      |
| Manage variables                      |         |            |             | ✓        | ✓      |
57
| Delete environments                   |         |            |             | ✓        | ✓      |
58 59 60
| Switch visibility level               |         |            |             |          | ✓      |
| Transfer project to another namespace |         |            |             |          | ✓      |
| Remove project                        |         |            |             |          | ✓      |
61 62
| Force push to protected branches [^2] |         |            |             |          |        |
| Remove protected branches [^2]        |         |            |             |          |        |
63

64
[^1]: If **Allow guest to access builds** is enabled in CI settings
65
[^2]: Not allowed for Guest, Reporter, Developer, Master, or Owner
66

67 68
## Group

69 70 71 72 73
In order for a group to appear as public and be browsable, it must contain at
least one public project.

Any user can remove themselves from a group, unless they are the last Owner of the group.

74 75 76 77 78 79 80
| Action                  | Guest | Reporter | Developer | Master | Owner |
|-------------------------|-------|----------|-----------|--------|-------|
| Browse group            | ✓     | ✓        | ✓         | ✓      | ✓     |
| Edit group              |       |          |           |        | ✓     |
| Create project in group |       |          |           | ✓      | ✓     |
| Manage group members    |       |          |           |        | ✓     |
| Remove group            |       |          |           |        | ✓     |
81 82 83

## External Users

84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101
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.