Ensure user counts are accurate across Gitlab
Problem
As a customer, I have no idea how many users are taking up active seats on my GitLab instance. There are multiple pages where user counts are recorded, and none of them seem to match up with one another.
GitLab reports user counts inaccurately. This makes it confusing and hard for customers to manage their users and collaborate well with GitLab at the time of renewal. True-ups are a significant difficulty for both GitLab and the customer due to these inaccurate user readings, and customers do not feel good about or trust their bill as a result.
Admin Dashboard | User Stats Page | Cohorts Page | Users Page | License Page |
---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
Max users = 108 (same as license page) total users = 137 (click blue button to go to user stats page) | Total users = 137 | ??? | Total users = Active 131 + blocked 3 = 134 | Total users (should say seats, users != paid seats = 108 |
Proposal
Research and understand the calculations and purpose of each page (see to-do list below), and put together a design proposal that provides clearer information and a better user experience for customers when trying to understand their user counts in relation to their bill.
To do
- Understand the purpose of each page and the problem it's trying to solve
- Understand where each page is pulling the data from and which page is the single source of truth (today)
- Revisit the requirement of each of these pages to display this information
- License page should display paid user information only. A user does not necessarily equate to a paid seat.
- Why do we show license information/user counts in two places?
- Understand how the
Users: 137
number is being calculated, why is it different to the users page? - Figure out how to align the users page with the admin dashboard in a way that makes sense.
- Ensure that their user accounts on
/admin/users
always show the full, accurate number (not 1000+ when it reaches over 1k). If this isn't possible we should consider whether that is the best place to display that information.
PLEASE NOTE The license page shown here is not the most recent license page designed for customers. #31948 (comment 220872238)
This is apparently the new one, which is not currently shown to customers due to a bug: !9785 (merged) (except some customers ssee it).
Related: