Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Category Direction - Subgroups

Stage Maturity Content Last Reviewed
Manage Complete 2020-10-12

Introduction and how you can help

Thanks for visiting this category page on Subgroups in GitLab. This page is being actively maintained by Melissa Ushakov. This vision and direction is a work in progress and sharing your feedback directly on issues and epics on GitLab.com is the best way to contribute.

Overview

Groups are a fundamental building block (a small primitive) in GitLab that serve to:

Our mission

In 2020, our goal is to make improvements by extending Subgroups to help enterprise organizations thrive on GitLab.com. We will accomplish that by iterating on existing constructs and streamlining workflows to guide users to intended usage patterns.

Challenges

Historically, enterprise customers have gravitated toward self-managed GitLab as their favored solution. With the proliferation of cloud services, enterprises are looking for options to use GitLab with managed infrastructure. We need to provide a SaaS platform that can safely and securely house our customers while reducing the load and cost of having to manage and configure their own infrastructure.

Opportunities

Iterating on subgroups will allow us to solve a number of problems with the current SaaS experience:

Target audience and experience

Groups are used by all GitLab users, no matter what role. However, heavier users of Groups in terms of organization and management of projects and users consist of:

What's Next and Why

The issues below have been prioritized to help solve the problems outlined in the Opportunities section.

What is Not Planned Right Now

Maturity

This category is currently Complete. The next step in our maturity plan is achieving a Lovable state.

Top internal customer issue(s)

🚨 GitLab Support Engineering: Isolation & Control Requirements

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license