What it is
The breakdown that shows whether an account is one person or a team. Each row carries that person's session count, active minutes over 30 days, when they were last seen, the module they spend the most time in, and the device class they last used.
Also called: who on the team uses it · single user account · which of my staff logs in
See it
How it works
- 1Sessions are grouped by user id with names taken from the most recent session that carried one.
- 2Last seen and last device come from the most recent session in the group.
- 3The per-person top module is the highest-total entry in their module map.
- 4Rows sort by active minutes descending.
Why we built it
It backs a specific retention rule elsewhere in the system — a single-user account is flagged because 'Only the owner is a member; team accounts retain far better.' Per-person usage is how that claim is checked rather than assumed.
The problem
- Seat adoption inside an account was unmeasurable.
- Team-wide rollout success could not be verified.
Sound familiar?
What you get
Shows whether a rollout actually reached the team.
Identifies the one person carrying the whole account.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →