The manager's cut of the same data. Deals, wins and win rate are attributed to the deal OWNER (the assignment snapshot on each event), while 'Moves' is attributed to the ACTOR who performed the move — so a manager who advances someone else's deal shows activity without stealing credit. Every column sorts, nulls always sort last.
Also called: who owns what · deals per rep · sortable rep table · win rate by owner
- 1Owner aggregates come from assigned_to_user_id; moves performed come from moved_by_user_id.
- 2A person appears on the board if they own deals OR performed moves.
- 3Names and roles resolve from the live roster, falling back to the denormalised snapshot on the log row when the identity provider is unreachable.
- 4Hidden entirely when the viewer's scope is 'own' — a rep who can only see their own leads sees no table of others.
Splitting owner from actor is deliberate: a stage move performed by a manager is activity for the manager and progress for the owner, and collapsing the two was producing both false credit and false idleness. The roster fetch is wrapped so a rate limit or outage from the identity provider degrades to snapshot names rather than blanking the table.
- Activity and ownership were conflated in every previous report.
- An identity-provider outage used to blank the names on the board.
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 →