Subgroups

Manage large projects easily with Subgroups

Documentation

Overview

GitLab is a fully integrated software development application that enables you and your team to work cohesively, faster, transparently, and effectively, from the discussion of a new idea through deployment and monitoring.

As a team-based collaboration platform, we're constantly enhancing GitLab's support for the most diverse teams and conditions. Looking on that direction, to leverage varied hierarchical team structures and applications architectures, we've created GitLab Subgroups.

With GitLab Groups you can assemble related projects together and grant members access to several projects at once. A subgroup, also known as nested group or hierarchical group, is essentially a group within a group. It has the same features a top-level group has, with some limitations.

Each group, at each level, is itself a first-class GitLab citizen, with the ability to have multiple projects. You can create up to 20 levels of subgroups, giving you an incredible level of flexibility.


How it works

  • Create a new group in GitLab, from which you can create subgroups.
  • Create a subgroup for one of your teams.
  • Add new projects into your subgroup.
  • You can now add members to your subgroup, who will automatically inherit their permission level to all the projects within their subgroup.
  • Mention your subgroup in any discussion (in issues, MRs, commits, snippets) and all its members will get a notification.

Benefits

  • Easily configurable: Once you create a subgroup, the only thing you need to set is the visibility level (public, internal, or private).
  • Maintain your workflow leveraged by GitLab: effectively organize your projects or teams within groups and subgroups so that you can easily add new members, change their access level, and create projects respecting your company's structure.

Take GitLab for a spin

See what your team could do with The DevSecOps Platform.

Get free trial

Have a question? We're here to help.

Talk to an expert
Edit this page View source