Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/project/members/share_project_with_groups.md')
-rw-r--r--doc/user/project/members/share_project_with_groups.md110
1 files changed, 52 insertions, 58 deletions
diff --git a/doc/user/project/members/share_project_with_groups.md b/doc/user/project/members/share_project_with_groups.md
index 52cc9fc4f9b..b9887212be0 100644
--- a/doc/user/project/members/share_project_with_groups.md
+++ b/doc/user/project/members/share_project_with_groups.md
@@ -9,83 +9,77 @@ info: To determine the technical writer assigned to the Stage/Group associated w
You can share projects with other [groups](../../group/index.md). This makes it
possible to add a group of users to a project with a single action.
-## Groups as collections of users
+For example, if `Project A` belongs to `Group 1`, the members of `Group 1` have access to the project.
+If `Project A` already belongs to another `Group 2`, the owner of `Group 2` can share `Project A`
+with `Group 1`, so that both members of `Group 1` and `Group 2` have access to the project.
-Groups are used primarily to [create collections of projects](../../group/index.md), but you can also
-take advantage of the fact that groups define collections of _users_, namely the group
-members.
+When a project is shared with a group:
-## Share a project with a group of users
-
-> - [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/247208) in GitLab 13.11 from a form to a modal
- window [with a flag](../../feature_flags.md). Disabled by default.
-> - Modal window [enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/247208)
- in GitLab 14.8.
-> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/352526) in GitLab 14.9.
- [Feature flag `invite_members_group_modal`](https://gitlab.com/gitlab-org/gitlab/-/issues/352526) removed.
-
-You can share a project only with:
-
-- Groups for which you have an explicitly defined [membership](index.md).
-- Groups that contain a nested subgroup or project for which you have an explicitly defined role.
+- All group members, including members of subgroups or projects that belong to the group,
+are assigned the same role in the project.
+Each member's role is displayed in **Project information > Members > Max role**.
+- The group is listed in the **Groups** tab.
+- The project is listed on the group dashboard.
-Administrators can share projects with any group in the instance.
+Be aware of the restrictions that apply when you share projects with:
-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.
+- [Groups with a more restrictive visibility level](#share-projects-with-groups-with-a-more-restrictive-visibility-level).
+- [Restricted sharing](#prevent-project-sharing).
-To share 'Project Acme' with the 'Engineering' group:
+## Share projects with groups with a more restrictive visibility level
-1. For 'Project Acme' use the left navigation menu to go to **Project information > Members**.
-1. Select **Invite a group**.
-1. Add the 'Engineering' group with the maximum access level of your choice.
-1. Optional. Select an **Access expiration date**.
-1. Select **Invite**.
+You can share projects only down the group's organization structure.
+This means you can share a project with a group that has a more restrictive
+[visibility level](../../public_access.md#project-and-group-visibility) than the project,
+but not with a group that has a less restrictive visibility level.
-After sharing 'Project Acme' with 'Engineering':
+For example, you can share:
-- The group is listed in the **Groups** tab.
-- The project is listed on the group dashboard.
-- All members, including members from the ancestors of the 'Engineering' group, gain access to 'Project Acme' with an access level based on the outcome of [maximum access level](#maximum-access-level).
+- A public project with a private group.
+- A public project with an internal group.
+- An internal project with a private group.
-When you share a project, be aware of the following restrictions and outcomes:
+This restriction applies to subgroups as well. For example, `group/subgroup01/project`:
-- [Maximum access level](#maximum-access-level)
-- [Sharing projects with groups of a higher restrictive visibility level](#sharing-projects-with-groups-of-a-higher-restrictive-visibility-level)
-- [Sharing project with group lock](#share-project-with-group-lock)
+- Can't be shared with `group`.
+- Can be shared with `group/subgroup02` or `group/subgroup01/subgroup03`.
-## Maximum access level
+When you share a project with a group that has a more restrictive visibility level than the project:
-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') only have 'Developer' access to 'Project Acme'.
-
-### Share a project with a subgroup
-
-You can't share a project with a group that's an ancestor of a [subgroup](../../group/subgroups/index.md) the project is
-in. That means you can only share down the hierarchy. For example, `group/subgroup01/project`:
+- The group name is visible to all users that can view the project members page.
+- Owners of the project have access to members of the group when they mention them in issues or merge requests.
+- Project members who are direct or indirect members of the group can see
+group members listed in addition to members of the project.
-- Can not be shared with `group`.
-- Can be shared with `group/subgroup02` or `group/subgroup01/subgroup03`.
+## Share a project with a group
-## Sharing projects with groups of a higher restrictive visibility level
+> - [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/247208) in GitLab 13.11 from a form to a modal
+ window [with a flag](../../feature_flags.md). Disabled by default.
+> - Modal window [enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/247208)
+ in GitLab 14.8.
+> - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/352526) in GitLab 14.9.
+ [Feature flag `invite_members_group_modal`](https://gitlab.com/gitlab-org/gitlab/-/issues/352526) removed.
-There are several outcomes you must be aware of when you share a project with a group that has a more restrictive [visibility level](../../public_access.md#project-and-group-visibility) than the project. For example, when you:
+You can share a project only with groups:
-- Share a public project with a private group.
-- Share a public project with an internal group.
-- Share an internal project with a private group.
+- Where you have an explicitly defined [membership](index.md).
+- That contain a nested subgroup or project you have an explicitly defined role for.
+- You are an administrator of.
-The following outcomes occur:
+To share a project with a group:
-- The group name is visible to all users that can view the project members page.
-- Owners of the project have access to members of the group when they mention them in issues or merge requests.
-- Project members who are direct or indirect members of the group can see group members listed in addition to members of the project.
+1. On the top bar, select **Main menu > Projects** and find your project.
+1. In the left navigation menu, select **Project information > Members**.
+1. Select **Invite a group**.
+1. **Select a group** you want to add to the project.
+1. **Select a role** you want to assign to the group.
+1. Optional. Select an **Access expiration date**.
+1. Select **Invite**.
-## Share project with group lock
+## Prevent project sharing
-It is possible to prevent projects in a group from
+You can prevent members of a group from
[sharing a project with another group](../members/share_project_with_groups.md).
-This allows for tighter control over project access.
+This restriction allows for tighter control over project access.
-Learn more about [Share with group lock](../../group/access_and_permissions.md#prevent-a-project-from-being-shared-with-groups).
+For more information, see [Prevent a project from being shared with groups](../../group/access_and_permissions.md#prevent-a-project-from-being-shared-with-groups).