Skip to main content

Dashboards

The portal has one role-aware overview, Home, and two dashboards that read a work area over a period: the Activity dashboard for delivery, and the Tooling dashboard for AI tool usage. This page explains what each shows and who sees what. For exact metric definitions, see the Metrics glossary.

  • Deployment: SaaS, On-premises

Every dashboard reads a single work area for a chosen period. What you see is shaped by your role and your work area membership. See Roles reference.

Home reshapes itself to who you are

ScreenshotHome page for a multi-area manager, showing the Activity across your work areas pulse strip and leaderboards for top AI tools, top AI spenders, and top AI adopters.

Home is a single overview page that shows a different set of tiles depending on who opens it:

  • System admins (Owner or Admin) see System health, covering license, integrations, and data freshness, and a comparison across their work areas.
  • Managers who own two or more work areas see Activity across your work areas: a summed pulse and cross-area leaderboards for top AI tools, top AI spenders, and top AI adopters.
  • Single-area admins see a Quick look at their one area.
  • Developers see Your activity: personal metrics for commits, coding time, AI sessions, and Agentic spend, their top tools, recent work branches, and a link to their full Developer profile.

The connection tile is not tracker status

Home shows a tile counting how many integrations are connected, for example "2 of 2 connected." It counts exactly two things: your source-control connection and your AI-analysis provider. It says nothing about whether any tracker is installed or reporting. A healthy fleet can sit beside "1 of 2 connected," and "2 of 2 connected" is fully compatible with zero developers reporting. Never use this tile to verify tracker setup. To check capture, use the developer roster or Validate data with developer traces.

The Activity dashboard shows delivery and work health

A work area's Activity tab, selected from the left nav under Work Areas. The Activity and Tooling tabs sit side by side under the work area name.

Activity dashboard Overview section with the eight KPI tiles: Active developers, Total coding time, Commits, Branch active-days, Sessions, Agentic adoption, Stale work, and Agentic spend.

The Activity dashboard answers what the team did and where work got stuck, for the selected period. It has these sections:

  • Overview: Branch active-days, active developers, agentic adoption (agent, CLI, and MCP use — narrower than overall AI adoption), Agentic spend, commits, sessions, stale work, and total coding time.
  • Trends: active developers, lines changed, commits, retained output, the human-versus-agentic work mix, and value per dollar (Output efficiency, VP/$) over time.
  • Activity patterns: a weekday-by-hour heatmap of when the team works. Times are stored in UTC and rendered in each viewer's own browser timezone.
  • Work health: work in flight by status, Review & merge flow, a needs-attention view of high-risk work and commit-to-push lag, and contribution mix.
  • Developer roster: a per-developer table. Selecting a name opens that person's Developer profile.

The Tooling dashboard shows which AI tools are used

Tooling dashboard Tool landscape section showing the Agentic tool usage bars and the metric toggle (Active time, Sessions, Tokens, Prompts).

The Tooling dashboard answers which AI tools and editors the team uses, how heavily, and by whom. It has these sections:

  • Overview: active developers, active time, prompts, and Agentic sessions.
  • Tool landscape: agentic tool usage by tool, with a toggle between active time, sessions, tokens, and prompts, and in-editor usage by editor, toggling between active time and sessions. The same editor can appear in both panels: a session counts as agentic when it ran through an agent or MCP tool, and as in-editor otherwise.
  • Sessions & activity: the agentic-versus-in-editor work-model split, tool-mix trend over time, agentic time by day of week, and average session duration by tool.
  • Developer roster: per-developer sessions, active time, tokens, prompts, value points, and Agentic spend, with an inline tool-mix bar. Selecting a name opens that person's Developer profile.

Which dashboards a work area shows

Not every work area type shows every surface. The following table lists what each renders:

Work area typeRenders
Team, Project, Mixed, CombinedActivity dashboard, Tooling dashboard
Company (the All Areas scope)Activity dashboard, Tooling dashboard, AI adoption report

The company-wide All Areas scope is the only one that carries the AI adoption report.