- Groups as collections of users
- Sharing a project with a group of users
- Maximum access level
- Share project with group lock
You can share projects with other groups. This makes it possible to add a group of users to a project with a single action.
Groups are used primarily to create collections of projects, but you can also take advantage of the fact that groups define collections of users, namely the group members.
The primary mechanism to give a group of users, say ‘Engineering’, access to a project, say ‘Project Acme’, in GitLab is to make the ‘Engineering’ group the owner of ‘Project Acme’. But what if ‘Project Acme’ already belongs to another group, say ‘Open Source’? This is where the group sharing feature can be of use.
To share ‘Project Acme’ with the ‘Engineering’ group:
For ‘Project Acme’ use the left navigation menu to go to Settings > Members
- Select the ‘Share with group’ tab
- Add the ‘Engineering’ group with the maximum access level of your choice
Click Share to share it
After sharing ‘Project Acme’ with ‘Engineering’, the project will be listed on the group dashboard
Note that you can only share a project with:
- groups for which you have an explicitly defined membership
- groups that contain a nested subgroup or project for which you have an explicitly defined role
Admins are able to share projects with any group in the system.
In the example above, the maximum access level of ‘Developer’ for members from ‘Engineering’ means that users with higher access levels in ‘Engineering’ (‘Maintainer’ or ‘Owner’) will only have ‘Developer’ access to ‘Project Acme’.
It is possible to prevent projects in a group from sharing a project with another group. This allows for tighter control over project access.
Learn more about Share with group lock.