Table of contents
3. Add non-group users to the project
1. The gitlab group
as the picture shows:
Private: only authorized users can see
Internal: As long as the user who logs in can see it
Public: Visible to any group and project
Two, gitlab users
as the picture shows:
Regular: can have the permissions of the group and project being joined
Admin: has all permissions
3. Assign users to groups
Take the assignment of test-user to Atlas-dev as an example, test-user will have the permissions of projects under the Atlas-dev group.
As shown, assigning allows you to choose what permissions this user has in this group; users have different capabilities depending on the level of access they have in a particular group or project. If the user is in both the group's project and the project itself, the higher permission level of the two is used.
GitLab CI/CD permissions depend on the user's role in GitLab. There are five roles: the permission level is from low to high, and the Owner has the highest permission;
Guest - Visitor
Reporter - Reporter
Developer - Developer
Maintainer - Maintainer
Owner - Owner
4. Permission introduction
1. Project member permissions
Different roles have different permissions
2. Group member permissions
Any user can remove themselves from a group unless they were the last owner of the group. The following table describes the various user permission levels within a group.
Parameter Description:
Browse group: Browse group information
Edit group: modify the group
Create subgroup: Create a subgroup
Create project in group: Create a group for the project
Manage group members: manage group members
Remove group: delete group
Manage group labels: manage group labels
3. Add non-group users to the project
Because test-user belongs to the Atlas-dev group, test-user will have project permissions under the Atlas-dev group. If the user is in both the group's project and the project itself, the higher permission level of the two is used.
Take test-user2 as an example. He is not in the Atlas-dev group. Now add him to the project database-mananger under the Atlas-dev group. When joining, he is required to set his role and role in this project The expiration time, if no expiration time is set, it will be permanent.
Here you can see that there are only four roles when adding new members directly to the project members, which is less than joining the group. Therefore, it is repeatedly emphasized that if the user is in the project of the group and the project itself at the same time, the higher permission level of the two will be used.
