Reference

Dashboard

The Overview dashboard is your organisation's agent operations on one screen: this month's usage and value, anything waiting on you, the health of your connections, and the latest runs.

What it shows

The dashboard leads with what your digital workforce delivered this month, not what it cost. Four summary cards sit at the top, each scoped to the current calendar month:

Provider cost and token-by-token spend are deliberately absent here. The dashboard is outcome-led. Token consumption against your plan stays visible as a governance guardrail under Settings → Billing.

Usage against your plan

The Runs this month card carries a meter showing usage against your plan's monthly run limit for the current billing period. The bar reports the honest figure but caps its width at 100%. It turns amber from 80% of the limit and red once you reach the cap.

When you are at or past 80%, a Manage plan link appears — but only if you hold the billing.manage permission. A plan with no limit set is treated as unlimited and shows no meter.

These are the same numbers, computed the same way, as the meters on Settings → Billing. The dashboard and the billing page never disagree on usage.

Key actions

The dashboard is a launchpad rather than a place you configure things. From here you typically:

Governance and permissions

Any active member may visit the dashboard, but the panels follow the rule that the interface hides what your permissions forbid while policies remain the real enforcer:

Everything you see here reflects the single tenant you are currently working in.

Health, runs and onboarding

Integration health surfaces only the connections that need attention: those reporting an unhealthy status (with a status badge and the last health-check time) and those with an expiring credential (with the expiry date). When every connection is healthy you see a single reassuring summary line; when none are connected you get a prompt to connect one.

Recent runs lists the five most recent executions across the organisation, each with its status, agent, trigger, who initiated it (or Scheduled for unattended runs) and how long ago it started. An empty state offers a route to browse agents.

Onboarding shows a guided checklist while your tenant is being set up. It disappears once dismissed, and once every step is complete it is acknowledged permanently so an established tenant never sees it resurface.

Next steps