debian-mirror-gitlab/doc/user/group/index.md
2023-06-20 00:43:36 +05:30

4.1 KiB

stage group info
Data Stores Tenant Scale To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments

Groups (FREE)

In GitLab, you use groups to manage one or more related projects at the same time.

You can use groups to manage permissions for your projects. If someone has access to the group, they get access to all the projects in the group.

You can also view all of the issues and merge requests for the projects in the group, and view analytics that show the group's activity.

You can use groups to communicate with all of the members of the group at once.

For larger organizations, you can also create subgroups.

For more information about creating and managing your groups, see Manage groups.

NOTE: Self-managed customers should create a top-level group so you can see an overview of your organization. For more information about efforts to create an organization view of all groups, see epic 9266. A top-level group can also have one complete Security Dashboard and Center, Vulnerability and Compliance Report, and Value stream analytics.

Group visibility

Like projects, a group can be configured to limit the visibility of it to:

  • Anonymous users.
  • All authenticated users.
  • Only explicit group members.

The restriction for visibility levels on the application setting level also applies to groups. If set to internal, the explore page is empty for anonymous users. The group page has a visibility level icon.

Administrator users cannot create a subgroup or project with a higher visibility level than that of the immediate parent group.