Reference
Control Centre
One read-only page that pulls together what your agents are doing right now: recent runs, pending approvals, outcomes and alerts, all so you don't have to check five screens.
What the Control Centre is for
The Control Centre brings together what otherwise lives across the Dashboard, Insights, Approvals, Runs and Audit Log pages into one read-only console. It is the place to answer "what is my workforce doing right now, and does anything need me?" without hopping between screens.
Everything on the page is a read-only summary. You do not approve, run or edit anything here directly; instead each panel deep-links you to the right place to act. The whole view summarises a fixed recent window of the last 30 days, so it always reads "right now" rather than a configurable analysis period.
Sandbox runs are excluded. Every figure and list omits sandbox dry-runs, so the Control Centre reflects only real, production activity from your workforce.
Outcomes and activity snapshot
The headline cards lead with what your workforce delivered over the window:
- Time saved: an estimate of manual effort offloaded (executed actions multiplied by an assumed minutes-saved-per-action). A coarse guide, not a measured figure.
- Estimated value: that time saved valued at your configured hourly rate. Indicative guidance, not an invoice.
- Work delivered: the total runs carried out, with the count of actions executed.
- Reliability: of runs that reached a decisive end (completed or failed), the share that completed. Cancellations are excluded.
Below the cards, the effort split bar shows how the workforce divided its work between actions auto-handled by the governance gate and those human-reviewed. It is a quick read on how much was routed through people.
Pending approvals and governor alerts
Two side-by-side panels surface what needs a human:
- Pending approvals shows the live count of actions waiting for a decision plus the oldest still waiting (the fairness signal — longest-waiting first). It links straight to the Approval Centre.
- Governor alerts flags two things: approvals that have passed their expiry window (sitting unattended past deadline until the per-minute sweep retires them), and integration health issues: connections that are unhealthy or credentials nearing expiry.
When nothing is amiss the alerts panel reads "No alerts — approvals are within their window and integrations are healthy."
Needs attention, activity and failures
Three lists help you triage:
- Needs attention: runs that completed cleanly but did not achieve their objective (a blocked or partial outcome, for example an agent that gave up because a channel or integration was missing). These read as success on status alone, so they get their own prominent list with the reason shown.
- Activity: a single cross-agent timeline of the most recent runs and approval decisions, newest first; the "what is happening" pulse.
- Failures: recent failed runs and failed actions, plus a roll-up of failed runs grouped by agent so the worst offender stands out.
Absolute timestamps are rendered in your tenant timezone, shown beneath the page.
Governance and access
The Control Centre is gated by the
runs.view permission — it is a read-only
operational view over run data, so it introduces no new
permission of its own. Every figure flows through tenant
scoping, so another tenant's data can never appear.
The page also respects per-permission visibility: the
integration-health portion of governor
alerts is only shown to holders of
integrations.manage (other governors still see
the overdue-approvals alert), and links such as "Open
Approval Centre", "View runs" and "View integrations" appear
only when you hold the matching permission. Because it is
read-only, no action you take here passes through the
approval gate or writes to the audit log; the pages it links
to do.