Instead of calling it licensed utilization chart, I suggest we call registered users count graph. It's helpful to know how the total registered users go over time on both OSS and licensed deployments.

We can put a horizontal line to indicate the limit for licensed deployments.

Additionally, we should consider creating a license utilization chart and adding it directly below this chart. That work will be tracked in another issue.

Instead of calling it licensed utilization chart, I suggest we call registered users count graph. It's helpful to know how the total registered users go over time on both OSS and licensed deployments.

We can put a horizontal line to indicate the limit for licensed deployments.

I just added these to this issue as should have and nice to have. We want to remove the confusion quickly, but if the should haves are relatively easy we get to do that now too. If it is more difficult, we can extract to a separate issue.

I totally agree that with just the should have, many users may still confuse that chart as utilization and registered users would be a very useful chart.

@BrunoQuaresma do you think it is possible to do the "must have" part at least before the release? The "should have" can follow after the release as subsequent PRs?

@bpmct sure thing. I just would need the copy for the "Explain in the tooltip that this is for measuring user activity and has no connection to license consumption".

Since we are touching on this part of the UI, I think would be nice to have some thoughts from @chrifro on how to better display this data to the user.

Add a new "Registered Users" chart as the first graph on the top with the upper limit bar, with the existing active users graph below it with no upper limit bar

This should be on /deployment/general page right?

I don't think we need much redesign, we can use the existing graph component for "registered users" IMO.

We said the same about the forgot password 😆 I would like to have @chrifro decide.

👋 I'd suggest that we add a design polish as a "nice to have". It shouldn't block the content changes that are requested by the customer and are more time-sensitive. At the same time, we can definitely make the graph visually more appealing and help to grasp the information quickly.

Some ideas:

• use a chart design similar to shadcn
• we could use the design with two lines (one for active user/per day and one for total registered users). The registered user graph could include a split for "suspended" and "dormant" users in the tooltip
• extend the timeframe from the last two months to all-time data
• allow filtering for days, weeks, months, and years. Maybe show monthly by default

I could create the design early next week. Let me know if I should focus on that.

Btw, thanks for the the great issue description @stirby, makes it easy to dive into this 🙏

FYI not a "must-do" anymore

@chrifro from the shadcn example charts, do you have a type preference? I think for this case, a stacked area chart could work very well. What do you think?

@chrifro from the shadcn example charts, do you have a type preference? I think for this case, a stacked area chart could work very well. What do you think?

That's exactly the one I had in mind as well 👌
Note: I didn't look into a design for this as I didn't hear back on the priority. Let me know if you need/prefer a mockup

Maybe something like

This is AI generated at https://v0.dev

Here’s the current situation: we have not implemented a redesign for the charts or this page, so I'm focusing on making only the necessary changes. @chrifro, please let me know if you would like to redesign the component now or if you prefer to do it later.

EDITED: I just realized that we need the total number of registered users, not just the new users. Making the correction now...

We can stick to your version for now. It's a great improvement ✨

For the colors, are you using existing colors? If not, could you use the blue and green that are defined in the new design system?
For dark theme (see Figma for light theme)
blue-bg: ##082f49
blue-highlight: #38bdf8
green-bg: #052e16
green-highlight: #BBF7D0

Related issue #14780

Yep, we need a chart that shows the total users against the seat count. We do not have to put everything in the same chart, however.

Potential partial blocker that I need input on. In short, I need to propose that we opt for a point in time gauge instead of a graph over time for total users against seat count. At least for this release.

This is because:

We don't track history for when users change status. We can't accurately display historical license count, because we only know whether a user is dormant or active today. We don't know when that changed. The same goes for when users where deleted. We know whether or not they were deleted. We don't know when they were deleted.

I can get a gauge done by release. The changes that need to be made to the db schema to support historical stats for dormancy and deletion require more consideration.

cc @matifali @chrifro @mafredri

Potential partial blocker that I need input on. In short, I need to propose that we opt for a point in time gauge instead of a graph over time for total users against seat count. At least for this release.

We already have a point-in-time value for registered users on the /deployment/licenses page. See the screenshot or are you talking about something else?

Yep, we need a chart that shows the total users against the seat count. We do not have to put everything in the same chart, however.

What we need new is as @bpmct said a new chart to show the growth of registered users.

Can you paste a mockup of what is your proposal for what to put in this release?

What you've pasted there is what I had in mind. I'm glad we already have it.
As for the requirement of graphing over time:

Do we care about registered users or about license utilization? The original problem statement above is this:

This misleads admins into thinking this is a way to gauge license usage over time

If we just want registered users over time regardless of whether or not they are consuming a license, then I can go ahead and fulfil the requirement. If we care about license utilisation, then I need to make larger changes to the DB schema that will take time.

https://coder.com/docs/admin/users#:~:text=Dormant%20accounts%20do%20not%20count%20towards%20the%20total%20number%20of%20licensed%20seats%20in%20a%20Coder%20subscription%2C%20allowing%20organizations%20to%20optimize%20their%20license%20usage

Based on the conversations above, I've created this issue:
#15740 (comment)

I created a new one because I would like to clarify priority for the remaining graph. It would be easier to track in isolation.

It specifically captures the outstanding feature and documents how to achieve it. Everything else in this current issue has been accomplished.

I propose we close this issue and shift it's focus to the new one. Objections?

I am ok with closing this. But we can keep it open to track the nice to haves.
cc: @stirby

Keeping open until we have a new time series graph for license utilization.

Latest mockup for the next iteration:

Notes:

• A tooltip would explain the meaning of active, dormant and suspended. It would mention that only active users consume a license seat.
• I've tweaked the wording on the bottom graph to mention activity, not active users, because active users has a specific meaning, with which activity cannot be confused
• The issue mentioned a specific charting library. I stuck with the one we're currently using for visual consistency.
• As long as the green line is below the white line, the user is in a valid state. Red and gray are allowed to exceed the white line because they do not consume license seats.
• If any of the three exceeds the user limit annotation line (white), then we can switch iconography and border colors to warning orange. if active exceeds the limit, we can switch to error red
• TODO: I'd like to give the lines a background to more explicitly show that the lines are stacked.

Status update:
Backend work up for review:
#16019
Frontend work WIP, but visible here:
https://github.com/coder/coder/pull/15893/commits/494f1651ed6b4fe2eb3caa4159c87413[…]ilters%5B%5D=.ts&file-filters%5B%5D=.tsx&show-viewed-files=true

Status update. Changes have been merged that allow the database and backend to support this feature. A frontend PR is ready, but designs have since shifted and some more work on the frontend is required. To my knowledge, @BrunoQuaresma has agreed to support here. I've co-assigned him to the issue.

@SasSwart @BrunoQuaresma Can you describe the scope of remaining changes for transparency purposes? Unless they are documented somewhere else.

The design has been updated and should now follow the design outlined here.

The General page is going to use the old API, but we rename the series on the UI to unconfuse the users. We also add additional explanation box.

The new API that Sas created is for the License page. In scope of the discussion we decided to use only the "Active Users" series from the API, so the "dormant" and "suspended" users will not be displayed. But the active users there are in fact the "users consuming the license seats" which is different from the "General page", where we show the daily user engagement.

To sum up:

• general page: use old API that was there before
• license page: use new API that Sas created, but only for the "active" series.
• we need to touch both of the screens with the changes, consequently