- Use cases
- Issues and merge requests within a group
- Create a new group
- Add users to a group
- Request access to a group
- Add projects to a group
- Transfer projects into groups
- Sharing a project with a group
- Manage group memberships via LDAP
- Group Security Dashboard
- Transferring groups
- Group settings
- User contribution analysis
- Issues analytics
- Dependency Proxy
With GitLab Groups you can assemble related projects together and grant members access to several projects at once.
Groups can also be nested in subgroups.
Find your groups by clicking Groups in the top navigation.
The groups dropdown in the top navigation was [introduced][ce-36234] in GitLab 11.1.
The Groups page displays all groups you are a member of, how many projects it holds, how many members it has, the group visibility, and, if you have enough permissions, a link to the group settings. By clicking the last button you can leave that group.
You can create groups for numerous reasons. To name a few:
- Organize related projects under the same namespace, add members to that group and grant access to all their projects at once
- Create a group, include members of your team, and make it easier to
@mentionall the team at once in issues and merge requests
- Create a group for your company members, and create subgroups
for each individual team. Let’s say you create a group called
company-team, and among others, you created subgroups in this group for each individual team
- When you start a new implementation from an issue, you add a comment:
@company-team, let’s do it!
@company-team/backend-teamyou’re good to go!”
- When your backend team needs help from frontend, they add a comment:
@company-team/frontend-teamcould you help us here please?”
- When the frontend team completes their implementation, they comment:
@company-team/backend-team, it’s done! Let’s ship it
- When you start a new implementation from an issue, you add a comment: ”
- Create a group for your company members, and create subgroups for each individual team. Let’s say you create a group called
In GitLab, a namespace is a unique name to be used as a user name, a group name, or a subgroup name.
For example, consider a user named Alex:
- Alex creates an account on GitLab.com with the username
alex; their profile will be accessed under
- Alex creates a group for their team with the group name
alex-team; the group and its projects will be accessed under
- Alex creates a subgroup of
alex-teamwith the subgroup name
marketing; this subgroup and its projects will be accessed under
By doing so:
- Any team member mentions Alex with
- Alex mentions everyone from their team with
- Alex mentions only the marketing team with
For a list of words that are not allowed to be used as group names see the reserved names.
You can create a group in GitLab from:
The Groups page: from the top menu, click Groups, and click the green button New group:
Elsewhere: expand the
plussign button on the top navbar and choose New group:
Add the following information:
- The Group name will populate the URL automatically. Optionally, you can change it.
This is the name that is displayed in the group views.
The name can contain only:
- Alphanumeric characters.
- Dashes and dots.
- The Group URL, which will be the namespace under which your projects will be hosted.
The URL can contain only:
- Alphanumeric characters.
- Dashes and dots. It cannot start with dashes or end in dot.
- Optionally, you can add a brief description to tell others what this group is about.
- Optionally, choose an avatar for your group.
- Choose the visibility level.
Add members to a group by navigating to the group’s dashboard, and clicking Members:
Select the permission level and add the new member. You can also set the expiring date for that user, from which they will no longer have access to your group.
One of the benefits of putting multiple projects in one group is that you can give a user to access to all projects in the group with one action.
Consider we have a group with two projects:
- On the Group Members page we can now add a new user to the group.
- Now because this user is a Developer member of the group, he automatically gets Developer access to all projects within that group.
If necessary, you can increase the access level of an individual user for a specific project, by adding them again as a new member to the project with the new permission levels.
As a group owner you can enable or disable non members to request access to your group. Go to the group settings and click on Allow users to request access.
As a user, you can request to be a member of a group. Go to the group you’d like to be a member of, and click the Request Access button on the right side of your screen.
Group owners and maintainers will be notified of your request and will be able to approve or decline it on the members page.
If you change your mind before your request is approved, just click the Withdraw Access Request button.
There are two different ways to add a new project to a group:
Select a group and then click on the New project button.
You can then continue on creating a project.
While you are creating a project, select a group namespace you’ve already created from the dropdown menu.
Group owners or administrators can allow users with the Developer role to create projects under groups.
By default, Developers and Maintainers can create projects under a group, but this can be changed either within the group settings for a group, or be set globally by a GitLab administrator in the Admin area at Settings > General > Visibility and access controls.
Available settings are
Developers + Maintainers.
Learn how to transfer a project into a group.
You can share your projects with a group and give your group members access to the project all at once.
Alternatively, you can lock the sharing with group feature.
In GitLab Enterprise Edition it is possible to manage GitLab group memberships using LDAP groups. See the GitLab Enterprise Edition documentation for more information.
Introduced in GitLab Ultimate 10.2.
Epics let you manage your portfolio of projects more efficiently and with less effort by tracking groups of issues that share a theme, across projects and milestones.
Get an overview of the vulnerabilities of all the projects in a group and its subgroups.
Introduced in GitLab Ultimate 11.9 behind the
Configure the Insights that matter for your groups or projects to explore data such as triage hygiene, issues created/closed per a given period, average time for merge requests to be merged and much more.
From GitLab 10.5, groups can be transferred in the following ways:
- Top-level groups can be transferred to a group, converting them into subgroups.
- Subgroups can be transferred to a new parent group.
- Subgroups can be transferred out from a parent group, converting them into top-level groups.
When transferring groups, note:
- Changing a group’s parent can have unintended side effects. See Redirects when changing repository paths.
- You can only transfer groups to groups you manage.
- You will need to update your local repositories to point to the new location.
- If the parent group’s visibility is lower than the group’s current visibility, visibility levels for subgroups and projects will be changed to match the new parent group’s visibility.
- Only explicit group membership is transferred, not inherited membership. If the group’s owners have only inherited membership, this would leave the group without an owner. In this case, the user transferring the group becomes the group’s owner.
Once you have created a group, you can manage its settings by navigating to the group’s dashboard, and clicking Settings.
Besides giving you the option to edit any settings you’ve previously set when creating the group, you can also access further configurations for your group.
Changing a group’s path can have unintended side effects. Read how redirects will behave before proceeding.
If you are vacating the path so it can be claimed by another group or user, you may need to rename the group name as well since both names and paths must be unique.
To change your group path:
- Navigate to your group’s Settings > General.
- Enter a new name under “Group path”.
- Hit Save group.
Add a security layer to your group by enforcing two-factor authentication (2FA) to all group members.
Prevent projects in a group from sharing a project with another group. This allows for tighter control over project access.
For example, consider you have two distinct teams (Group A and Group B) working together in a project. To inherit the group membership, you share the project between the two groups A and B. Share with group lock prevents any project within the group from being shared with another group. By doing so, you guarantee only the right group members have access to those projects.
To enable this feature, navigate to the group settings page. Select Share with group lock and Save the group.
With Member lock, it is possible to lock membership in a project to the level of members in the group.
Member lock lets a group owner lock down any new project membership to all the projects within the group, allowing tighter control over project membership.
For instance, if you want to lock the group for an Audit Event, you enable Member lock to guarantee that membership of a project cannot be modified during that audit.
To enable this feature:
- Navigate to the group’s Settings > General page.
- Expand the Permissions, LFS, 2FA section and select Member lock.
- Click the Save changes button.
This will disable the option for all users who previously had permissions to operate project memberships so no new users can be added. Furthermore, any request to add a new user to a project through API will not be possible.
Group file templates allow you to share a set of templates for common file types with every project in a group. It is analogous to the instance template repository feature, and the selected project should follow the same naming conventions as are documented on that page.
Only projects that are in the group may be chosen as the source of templates. This includes projects shared with the group, but excludes projects in subgroups or parent groups of the group being configured.
This feature may be configured for subgroups as well as parent groups. A project in a subgroup will have access to the templates for that subgroup, as well as any parent groups.
To enable this feature, navigate to the group settings page, expand the Templates section, choose a project to act as the template repository, and Save group.
Define project templates at a group-level by setting a group as a template source. Learn more about group-level project templates.
- Projects: view all projects within that group, add members to each project, access each project’s settings, and remove any project from the same screen.
- Webhooks: configure webhooks to your group.
- Kubernetes cluster integration: connect your GitLab group with Kubernetes clusters.
- Audit Events: view Audit Events for the group.
- Pipelines quota: keep track of the pipeline quota for the group.
With GitLab Contribution Analytics you have an overview of the contributions (pushes, merge requests, and issues) performed by your group members.
With GitLab Issues Analytics, in groups, you can see a bar chart of the number of issues created each month.
Use GitLab as a dependency proxy for upstream Docker images.