|Labels||permissions, user management, user management|
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:
Any user of GitLab could be considered a relevant audience, but improvements in this area likely think about two specific instances:
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.
As with any category in GitLab, it's dependent on your ongoing feedback and contributions. Here's how you can help:
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, it’s imperative that EE instances are able to use their license seats efficiently - this typically involves grooming 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.