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

Category Direction - Teams

Category Attribute Link
Stage Manage
Maturity Not applicable
Labels Category:Teams

Teams

Groups in GitLab are intentionally flexible. They're a great way of creating organization and access control, and do a good job of being a relatively generic object that's effective at both managing projects and organizing groups of people. In fact, our hypothesis is that these are the two big buckets that users tend to lean on groups for:

While we do a solid job on the former, we've got room to improve on the latter. Since groups do double-duty here and are relatively generic objects, we're losing an opportunity to refine specific features that might help people get work done. Specifics on where we see this evidenced:

Target audience and experience

Whilst we can assume that all users would benefit from the Team experience, the target personas we are focusing on are Team Leaders, Group Owners & System Administrators.

Current focus

Please see the Create and manage a team in GitLab epic.

Maturity

For the moment, Teams are considered a non-marketing category without a maturity level that can be compared to other competing solutions.

How you can help

As with any category in GitLab, it's dependent on your ongoing feedback and contributions. Here's how you can help:

  1. Comment and ask questions regarding this category vision by commenting in the public epic for this category.
  2. Find issues in this category accepting merge requests. Here's an example query!