Navigating the dashboard
- Left rail: Projects (your organization’s home), then the project’s pages — Overview, Sessions, Users, Skills, MCP, Burn map, Pull requests, Metrics (Dashboards, Explore), and Models (Usage, Compare). Settings sits at the bottom.
- Top bar: switch organization or project, create a new one, and see the live status of the page’s data (Ready, Updated, Refreshing…).
Period and cost view
Two controls in the page header apply across the dashboard, and your choice is remembered:- Period:
24h,7d, or30d(the default). - Usage view: Tokens, Notional (the default), or Net. See Cost views for what each one counts.
Headline and live burn rate
The top card shows Spend (or Tokens) for the period, with its trend against the period before, and how much of it a subscription covered versus metered billing. Below it are the period’s Tokens, Sessions (with turns), Active users (with API keys), and PRs merged, plus a token activity calendar. Burn rate now is live: tokens per minute and dollars per hour over the last 60 seconds, the number of calls in that minute, a last-hour sparkline by token type, and Burn by model and Burn by user rankings.Breakdowns
Below the headline, the period is compared with the one before it:
Select a source in Spend by source to open that source’s page: its tokens, sessions, active users, and model calls, spend over time, and its models, providers, principals, and sessions.
Banners
The Overview tells you when something needs attention:- Funding gap — people are running an agent without plan usage being captured, so Terma cannot tell what a subscription covered. The fix is to install the Terma CLI for them.
- Unmapped principals — identities that are not mapped to a member of your organization. See Principal mapping.
- Connect GitHub — pull request data needs the GitHub connection. See Pull requests.
From the CLI
The same numbers are available in a terminal:terma usage reports provider cost, which corresponds to the Notional view.