Documentation menu
Dashboard & analytics
Managed runners
Team & notifications
Billing & plans
Workflow files
The dashboard at a glance
The dashboard layout, every sidebar destination, the filters on Command & Control, and the banners that tell you what Latchkey is doing in the background.
In short
- The Overview leads with AI Insight: what self-heal fixed in the last 30 days and the findings ready for your approval.
- The sidebar covers analytics, runners, insights, team, billing, and settings; admin-only items are marked.
- Command & Control, Performance and Cost draw the shared filters: Filters for repositories and workflows, and the Date range window in the title bar. Performance also draws a Runners select, which narrows no other page.
- Data refreshes automatically, and faster while workflows run; charts expand to fullscreen with filters intact, except Usage value, which no filter narrows.
- Banners carry account notices: free-tier warnings and trial notices.
The Command & Control page at the Pro level, as an owner sees it. The title bar holds the date window set to 30d, Export, and Apply all 1. AI Insight: Self-heal · last 30 days, Autonomous, 39 failures healed on the runner, 1,240 min of re-runs avoided and $3.10 not spent at list rate, the healed failures by category (network 18, memory 9, disk 4, missing tools 6, config drift 2), and 2 failures left for you beside Outcome report. Beside it, Insight · ready to apply, with a 5 open findings chip: 1 finding ready to apply, the line 1 ships as a pull request now. 2 need an engineer: self-heal could not fix them., the open findings by pillar (Cost 0, Security 1, Reliability 4, Adoption 0), and Refreshed nightly beside Review 5 findings. Below it, Pipeline performance: workflow health 84% successful, down 4 pts on the prior 30 days, on a meter with its 50% threshold; 322 total runs, up 18%; average duration 4m 12s, 9% faster; mean time to recovery 3m, down 1m. While a workflow runs, a network failure that self-heal fixed raises the healed count to 40 and the run total to 323, without a reload.
The dashboard has three standing parts: the sidebar (where you go), the title bar (which page you are on, with its tools), and the page itself. This guide covers the sidebar and the filters on Command & Control, plus the banners Latchkey uses to tell you what is happening in the background.
The sidebar#
Every destination in one place. Entries marked admin are only visible to workspace owners and admins; everyone else sees the rest.
The Account and help menu opens from the person at the foot of the sidebar. It holds Profile and Refer & Earn under Account, Show decimals under Display, Use cases and tips, Docs, Support, Send feedback and Take the tour under Help, and Sign out. Send feedback opens a dialog.
Command & Control of the acme workspace on its first visit after setup, at the Easy level. A Tour card over the page reads Welcome to Latchkey: This tour shows each page of the dashboard and the controls around it, one step at a time. It opens again from the Account and help menu, with Skip for now and Start tour. The tour starts: a card beside the workspace menu at the head of the sidebar reads Workspace menu, This dashboard shows one workspace at a time, the one named here. Its menu lists every workspace you belong to, with your role in each, Step 1 of 21, with End tour and Next. Next moves the card beside the notifications bell: Notifications, Everything Latchkey notifies you about lands here, whatever your channel settings. The badge counts what you have not read, Step 2 of 21, now with Back, End tour and Next. The figure then skips to the last card: Tour complete, You are all set, Command & Control is where the dashboard opens. This tour opens again from the Account and help menu, with Go to Command & Control.
Filters on Command & Control#
Command & Control, Performance and Cost draw the shared filters, and a choice made on one carries to the others:
- Repository and Workflow selects. The repository select adds search, select-all, and clear-all. In Pro they sit in a Filters row, with a chip for each filter that narrows the data. In Easy they sit in the popover of the Filters button in the title bar. While no repository is selected, the workflows select reads "Select a repository first".
- Date range window in the title bar with 7d, 30d and 90d. Pro adds Custom, which opens the picker with 1Y, YTD and a calendar range. The default window is the last 30 days, today included.
- Reset filters to go back to defaults in one click.
How the filters compose#
The repository, workflow and date selectors narrow the same result set: repository and workflow act together, and the date range bounds the window everything is computed over. Selecting one repository and one workflow, then tightening the date range, is the standard way to isolate a single pipeline's behavior over a specific stretch of time. Command & Control, Performance and Cost draw these filters, and every run and job figure they narrow counts only what Latchkey served. On Command & Control, the AI Insight and Cost sections read the whole workspace, and say so while a filter narrows the page.
- Command & Control does not guess a scope for you
- The workflows select is disabled and reads "Select a repository first"
- The repositories select fills the page once a repository is chosen
- Command & Control shows data for exactly the repositories and workflows you chose
- The workflows select and the Date range window narrow it further
- Reset filters takes you back to defaults in one click
If a repository you expect is missing from the selector, it is most likely not monitored yet. Monitoring is managed by owners and admins from Settings, Code hosts, Enrol repositories; see Managing repositories.
Fullscreen charts and live refresh#
Two behaviors worth knowing about the data on screen. On Command & Control, Successful builds, Run outcomes and Usage value expand to a fullscreen view; the two pipeline charts keep the filters there, so you can slice and present in the same view without losing your scope, while Usage value, which no filter narrows, draws none. And the page refreshes automatically, shortening its refresh interval while any workflow is in progress: during active CI runs, results land in near real time with no manual reload.
Banners worth knowing#
- Free tier warning: appears when you have used 80% (and again at 100%) of your included runner minutes.
- Trial notices: a countdown when your trial is ending, and a full-screen prompt to subscribe once it has ended.
None of these require action to keep the dashboard working. Each one has a natural next stop when you want more detail:
| Banner | What it tells you | Where to go next |
|---|---|---|
| Free tier warning | You have used 80% (then 100%) of your included runner minutes | Runner usage and free minutes |
| Trial notices | Your trial is ending, or has ended | Plans and trial |
Command & Control (Overview)#
The Overview leads with what Latchkey did for you and what is waiting on your decision, then compresses performance and cost below it. Three sections, top to bottom, each linking to its full page:
- AI Insight (link "View AI Insight"): the hint reads "What self-heal fixed on its own, and the findings waiting for your yes." A strip of two cells shows Self-heal · last 30 days with an Autonomous chip: the failures healed on the runner, the minutes of re-runs avoided and what they would have cost at list rate (in Pro), the healed failures by category, and the failures left for you beside an Outcome report link. Beside it, Insight · ready to apply counts what Apply all would take as pull requests (in dollars a month when they carry savings), under a chip counting every open finding; it says what ships now and what needs an engineer (in Pro), lists the open findings for each of cost, security, reliability and adoption, and links to AI Insight with Review findings and their count. Below the strip, the top three open findings appear as cards with their actions: Preview, a one-click apply such as Pin to SHA, Dismiss, or Investigate. When nothing is open, the section reads "No open findings. Latchkey checks nightly." Owners and admins also see Apply all in the title bar.
- Pipeline performance (link "View performance"): four figures, each against the window before it: Workflow health with a meter and its 50% threshold, Total runs, Average duration and Mean time to recovery, the last three with a sparkline of their days. Below them, three panels: Successful builds by repository each day, Failing most by workflow, with the failed runs, the fail rate and the cancelled runs in its foot, and Run outcomes each day (Passed, Failed, Timed out, Stopped, and Cancelled · not run).
- Cost (link "View cost"): the hint reads "What runner minutes are worth this month, and how much the free allowance still covers." Usage value charts this month's runner minutes at list rate, used and projected, against what the free allowance is worth; beside it sits the Runner cost card (this calendar month's runner cost so far, the free minutes left, and what the jobs running now add to your bill an hour once your free minutes are used). Below them, Minutes by runner size and How minutes are counted, the free-minute weight of each size. The shared filters do not apply to this section, and while one narrows the page the section says so.
Reading the Overview in 60 seconds#
The Overview is built to be scanned, not studied. Here is one way to make a quick pass a habit; the order is a suggestion, not a product requirement:
Two numbers set the tone. The left number is what self-heal already fixed on its own; it needs nothing from you. The right number is what is ready to apply as a pull request, and the chip beside it counts every open finding; if either is not zero, that is your first stop. The full queue lives on AI Insight.
The top three open findings sit right below the hero with their one action on the card. Preview shows the exact change before you apply; Dismiss clears what does not apply to you. A minute here often empties the queue without leaving the Overview.
Look at Workflow health and its meter, Mean time to recovery, and the fail rate in the foot of Failing most. You are not looking for absolute numbers; you are looking for movement versus what is normal for your team, which each figure states against the window before it. Anything surprising, follow the section link into Performance.
Usage value shows where this month's runner minutes are heading at list rate against the free allowance; the dashed line runs on at this month's pace to the month's end. Glance at the Runner cost card for this calendar month; the free minutes left are on the same card, and a banner will also warn you at 80%. The full story lives on Cost.
Each Overview section links to its full page. A useful discipline: pick the single section that changed the most since your last look and go deep on that one, instead of skimming all three.
Q.01What do the dashboard filters apply to?
The shared Filters (repositories and workflows) and the Date range window scope Command & Control, Performance and Cost, and a choice made on one carries to the others. On Command & Control, the AI Insight and Cost sections read the whole workspace. Charts opened fullscreen keep the same filters; Usage value, which no filter narrows, draws none.
Q.02How often does dashboard data refresh?
Automatically, and faster while workflows are running, so you do not need to reload during a build. If a page looks empty, that is usually the filters, not missing data.
Q.03What are the banners at the top of the dashboard?
They are notices rather than errors: free-tier warnings as you approach the monthly minute allowance, and trial notices. Every blocked state has an explicit tell, so a silent dashboard is not a blocked one.