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

Category Direction - Users

Stage Maturity Content Last Reviewed
Manage Not Applicable 2020-10-22

Introduction and how you can help

Thanks for visiting this category page on Users in GitLab. The Users category is part of the Manage stage. 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

The concept of a user isn't a new one, but it touches a number of areas in GitLab that are critical to the success of our users. Namely:

Target audience and experience

Any user of GitLab could be considered a relevant audience, but improvements in this area likely think about two specific instances:

  1. Large EE instances: These are customers with large seat counts, who need the ability to understand who is using GitLab and who is not - and have the tools needed to manage these users at scale.
  2. GitLab.com: For individual contributors, the user profile becomes your identity as a developer. While concepts like the contribution graph or project list may not be of paramount importance to a self-managed enterprise user, individual developers on GitLab.com want their profile and presence on GitLab.com to represent them.

Maturity

As much about users in GitLab are application-specific, users are considered a non-marketing category without a maturity level that can be compared to other competing solutions.

What's next & why

Next: Due to other priorities for the Manage stage, we are not planning to make significant investments to the Users category in the 3-4 next milestones.

After: An area of focus in the future will be to make it easy to identify and manage inactive users. One of the most common tasks for an administrator is understanding and identifying the activity levels of their users. Since GitLab does not use a named license model, EE instances must be able to use their license seats efficiently - this typically involves refining membership periodically and handling inactive users. We should make this easy for organizations. It should be straightforward and unambiguous to identify these users, and easy to take appropriate action. Please see the inactive user management epic for more details.

Top user issue(s)

TBD

Top internal customer issue(s)

TBD

Top Vision Item(s)

TBD

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