Dashboard
Navigate to Dashboard from the sidebar. Everyone sees the same Environments Dashboard — an org-wide view of environment usage, bookings, and requests. Provisioners, Admins, and Super Admins additionally see a second Infrastructure Dashboard tab covering cloud connections and Terraform activity.
| Role | Environments Dashboard | Infrastructure Dashboard tab |
|---|---|---|
| Super Admin / Admin | ✓ (with cost data) | ✓ |
| Provisioner | ✓ | ✓ |
| User / Viewer | ✓ | — |
Environments Dashboard
Overview Cards
| Card | Shows |
|---|---|
| Total Environments | Total count + how many are currently available |
| Active Users | Active user count + total users in the org |
| Monthly Cost | Month-to-date environment cost + projected monthly total — Admin/Super Admin only |
| Active Bookings | Currently active bookings; click through to pending approvals |
| Total Bookings | All-time booking count |
| Total Environment Requests | All-time environment request count |
| Total Decommission Requests | All-time decommission request count |
Resource-limit warnings (e.g. approaching your license cap for environments or users) appear above the cards when relevant.
Pending Approvals
A banner card that only appears when there's something to act on — pending bookings, environment requests, decommission requests, and (Admin/Super Admin only) pending user invites — each as a clickable count that jumps straight to the filtered list.
Environment Status
A breakdown of all environments by operational status — Available, Occupied, and Maintenance — each with a count and percentage of total.
These tiles read each environment's recorded status, which is a different question from whether anything is running on it. A shared environment is only recorded as Occupied once every slot is taken, so one with three of ten teams in it still counts as Available here. For "how much of what we can book are we actually booking", see Environment Utilisation below.
Analytics Charts
- Booking Trends — daily bookings over the last 30 days and monthly bookings over the last 12 months
- Environment Distribution — breakdown by environment type, cloud provider (AWS, Azure, GCP, On-Premises), and sharing model (shared vs exclusive)
- Environment Utilisation — how much of your bookable estate is actually in use right now (see below)
- Top Users — the top consumers by booking count, with name, email, and team — visible to every role, not just Admins
Environment Utilisation
Answers one question: how much of the estate you can book are you actually booking right now. Every environment falls into exactly one of three counts.
| Count | What it means |
|---|---|
| In Use | Bookable environments with a booking running now |
| Idle | Bookable environments with nothing running |
| Excluded | Under maintenance, offline, preparing, or booking disabled |
Utilisation = in use ÷ (in use + idle). Excluded environments are left out of both halves — they can't hold a booking, so counting them would make the estate look permanently underused. Decommissioned environments aren't counted at all: they're gone rather than unavailable.
Two things worth knowing:
- In Use means a booking is genuinely running — not the environment's recorded status. A shared environment is only recorded as Occupied once it's at capacity, so one with three of ten teams in it counts as In Use here while the Environment Status tiles above still show it as Available. That's the same estate described two different ways, not a contradiction.
- In Use and Idle are one split; "has free capacity" is a different one. A shared environment with one booking and nine free slots is In Use, and the chart says nothing about the nine slots. It answers "is anything happening here", not "can I still get in".
A badge beside the title reads the rate back as a word:
| Band | Rate |
|---|---|
| Underutilized | Below 30% |
| Moderate | 30–59% |
| Efficient | 60–89% |
| Critical | 90% or above |
Critical means the estate is nearly full, not that anything is broken — at 90%+ the next request is likely to queue, which is a capacity-planning signal rather than a fault.
If there are no bookable environments at all, the chart reads No Data rather than 0% — nothing is being used because there's nothing to use, which is a different situation from an idle estate. The ⓘ beside the title carries these same definitions and the formula; click it to keep the panel open.
Environment Requests Queue
Lists up to 5 pending environment requests with requester name, environment type, and submitted date, with a link to review each one.
Cost Anomalies
Admin/Super Admin only. Shown when open FinOps anomalies exist, with counts by severity (Critical, High, Medium, Low) and a link to /finops/anomalies.
Booking Patterns Heatmap
Hour of day (0–23) vs day of week, showing when environments are booked most frequently.
Dashboard Settings
Click the settings icon (top-right) to toggle sections on or off: Overview cards, Environment status, Analytics charts, and the Heatmap. Preferences are saved in your browser.
Infrastructure Dashboard
Visible only to Provisioners, Admins, and Super Admins, as a second tab alongside the Environments Dashboard.
Overview Cards
| Card | Shows |
|---|---|
| Connections | Total cloud connections + active count |
| Terraform Projects | Total projects + active count |
| Successful Runs | Successful runs, all time |
| Failed Runs | Failed runs requiring attention |
Terraform Run Status Chart
A chart summarising recent Terraform run outcomes.
Recent Infrastructure
- Connections — the 5 most recent cloud connections with name, provider, project count, and status
- Terraform Projects — the 5 most recent projects with name, cloud provider, workspace count, and status
- Recent Terraform Runs — the last 10 runs with status icon, run name, run type (Plan/Apply/Destroy/Refresh), and timestamp
Quick Actions
- Manage Connections →
/connections - Manage Projects →
/terraform/projects - View All Runs →
/terraform/runs
