Team Console
The Team Console is the manager surface. It rolls up the same scores your users see into a team-level view across every team you manage, and routes you to the screen that addresses each signal.
Who can see it
Section titled “Who can see it”The console is role- and plan-gated — two conditions must both hold:
- Your org has the team plan (
teamfeature) enabled. - You manage at least one team (you hold the
managerrole on a team).
A manager who isn’t on the team plan, or a user who manages no team, sees a notice instead of the screens. This is a convenience gate — the API also enforces team scope server-side (a caller only ever sees teams they’re authorized for).
Managing is independent of being an org admin: a pure manager sees the four console screens; a pure admin/owner who manages no team sees only the Settings admin tabs (Users, Teams).
The four screens
Section titled “The four screens”Most screens share a team selector (a single team, or all managed teams) and a Day / Week / Month period toggle — but not all of them: Overview always spans every team you manage (no selector), and Reports covers one team at a time on a weekly basis (no period toggle).
| Screen | What it’s for |
|---|---|
| Overview | One-glance health hub across all managed teams |
| Performance | Member leaderboard and what each person worked on |
| Usage & Cost | Where spend concentrates, model mix, and inefficiency signals |
| Reports | An AI-written period briefing, exportable to Markdown or PDF |
Two graded numbers recur across the screens:
- Prompt Score — the Average Prompt Grade rescaled to 0–100, with a letter grade.
- Completion rate — crushed ÷ total scored sub-sessions (ungraded).
Team management (admin)
Section titled “Team management (admin)”Managing membership is separate from the console. It lives in the Settings section, opened from the account menu in the header: the Users and Teams tabs. These require an admin/owner role and the team plan, and are for managing membership rather than reading metrics.