Team Rollup
What every member's scheduled runs produced, rolled up for the team. The manager's read-only view of the work, scoped to your team.
Overview
The Team Rollup is the team-wide version of your personal Activity page. It aggregates every member's runs and brain state into one view so a manager can see what the team produced. It's read-only and scoped to your team, you only see members of teams you belong to. It carries run metadata and brain-state summaries, not the raw content of anyone's drafts.
Gated on login + team membership. If you're not on a team yet, you'll see an empty state; once members connect their tools and their scheduled runs start, their activity appears here.
What it shows
- What the team produced. Team-wide outcomes over the last 30 days, plus runs and actions week over week.
- By member. Each member's run count, actions, and rank, a leaderboard of who is putting their roles to work.
- By role (team-wide). Which roles the team leans on, how many members use each, and when each last ran.
- By account & deconfliction. When members tag their runs with an account, a per-account/per-member breakdown plus a "heads up, teammates worked the same account this week" collision flag (see below).
- Leaderboard (opt-in). A privacy-respecting scoreboard that ranks members on outcomes per run, quality of output, not who ran the most. Off by default; only the team owner can turn it on.
By account & deconfliction
When members' skills tag their runs with an account (the optional account_ref label they pass to emit_telemetry, a domain or account name), the team rollup surfaces two account-aware views:
- Heads up, teammates on the same account. A card at the top flags any account two or more teammates ran a role against in the last 7 days, "3 teammates worked
acme.comthis week", with who worked it, how many runs each, and their last run. It's the collision-avoidance signal: coordinate before two reps work the same account blind. The card appears only when an account is actually contested; a team where everyone is on separate accounts sees nothing (honest quiet state). - By account. A per-account, per-member breakdown over the last 30 days, each account your team worked, and the members who worked it with their run counts and last-run date. Contested accounts (2+ members) are marked. A dropdown filters the view to one account, and the "See activity" link on a heads-up card jumps straight to it.
Same posture as the rest of the rollup: account_ref is a free-text label, not a synced CRM record. Grouping is exact string match, so a team should agree on one convention per account (domain recommended). Deconfliction is a deterministic rule over the labels, no AI, reproducible from the run history. Honest empty state: until members' skills pass an account, the "By account" card explains what unlocks it and the heads-up card stays hidden. Whether a skill tags its runs is up to the product; see the API reference.
Leaderboard
The leaderboard (Phase 22.5) is an opt-in, owner-controlled scoreboard. Nothing shows until the team owner enables it from the rollup page. It ranks members on actions per run, the quality of what each run produced, rather than raw run counts, so volume alone never wins the board. A member needs at least a few runs in the last 30 days to place; everyone else is listed unranked with how many more runs they need, and an all-quiet team shows an honest empty state.
Aggregate-only, same as the rest of the rollup: it reuses the run counts already on this page, never revenue, never draft content. The enable/disable toggle is owner-gated; members see the board only once it's on.
Public shipping feed
Separate from the team view, individual members can opt in (from Settings, Account, Public shipping feed) to add their work, as anonymized, aggregate counts only, to the public shipping feed. It shows the day's totals across all consenting users ("50 accounts researched, 2 posts published"), never revenue, never account names, never per-user identity, and is hidden entirely below a small contributor floor so no single account can be picked out.
How to use it
- Spot who hasn't activated. A member with zero runs is licensed but not yet connected, a nudge, not a mystery.
- See what is actually driving output. The by-role view tells you where the team's leverage is coming from.
- Drill in. Open a member to see their individual rollup at
/team-admin/rollup/<userId>, their run totals, week-over-week trend, per-role breakdown, and outcomes over the last 30 days, all from the same telemetry the team view aggregates.
Team product seats
A team seat pack licenses a product for several teammates in one purchase. Buy one on the pricing page (GTM Engine, Content Engine, Founder Chief-of-Staff, or the Full Suite, 5 seats each, Company OS Core included per seat), and each seat grants the product to a teammate through their own account. Seats are ordinary entitlements, the products verify them exactly like a personal purchase.
- Auto-fill from your roster. On purchase, seats fill owner-first then by join order, up to the seats you bought. Members who join later take any free seat; members who leave free theirs automatically.
- Reassign as needed. The Team admin page shows each pack with seats used and free, and an Assign / Unassign button per member (owner only). Unassigning never removes a product a member bought for themselves.
Need more than 5 seats on a product? Buy a second pack, seats stack across packs.
Data & privacy
The work runs on our servers, on a schedule, and we process the data each member connects to do it, encrypted, isolated per tenant, never sold, never used to train models. The team view is the reporting layer on top: it carries run metadata and brain-state summaries, not the raw content of anyone's drafts.
Related
- Activity, your personal version of this view.
- Concepts, the rollup, how telemetry becomes a dashboard.
- Connect your tools, how members activate.