debian-mirror-gitlab/doc/workflow/share_projects_with_other_groups.md

33 lines
1.6 KiB
Markdown
Raw Normal View History

2016-06-02 11:05:42 +05:30
# Share Projects with other Groups
2016-09-13 17:45:13 +05:30
You can share projects with other groups. This makes it possible to add a group of users
to a project with a single action.
2016-06-02 11:05:42 +05:30
## Groups as collections of users
2016-09-13 17:45:13 +05:30
Groups are used primarily to [create collections of projects](groups.md), but you can also
take advantage of the fact that groups define collections of _users_, namely the group
members.
2016-06-02 11:05:42 +05:30
## Sharing a project with a group of users
2016-09-13 17:45:13 +05:30
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.
2016-06-02 11:05:42 +05:30
To share 'Project Acme' with the 'Engineering' group, go to the project settings page for 'Project Acme' and use the left navigation menu to go to the 'Groups' section.
2016-09-13 17:45:13 +05:30
![The 'Groups' section in the project settings screen](groups/share_project_with_groups.png)
2016-06-02 11:05:42 +05:30
Now you can add the 'Engineering' group with the maximum access level of your choice.
After sharing 'Project Acme' with 'Engineering', the project is listed on the group dashboard.
!['Project Acme' is listed as a shared project for 'Engineering'](groups/other_group_sees_shared_project.png)
## Maximum access level
!['Project Acme' is shared with 'Engineering' with a maximum access level of 'Developer'](groups/max_access_level.png)
In the screenshot above, the maximum access level of 'Developer' for members from 'Engineering' means that users with higher access levels in 'Engineering' ('Master' or 'Owner') will only have 'Developer' access to 'Project Acme'.