Organization Dashboard

Purpose: The Dashboard inside organisation Settings is the platform's analytics surface — cross-project and per-project bar charts plus a work-items table. This page walks the UI.

Where the Dashboard lives

The Dashboard is reached from organisation Settings — open Settings (the gear control on Home, with the right organisation selected in the header), then choose Dashboard in the left sidebar. It is shown only when you have analytics access for the organisation; engagement leads typically do, product engineers typically do not.

All figures and lists on the Dashboard refer to the organisation you had selected on Home before opening Settings. Switching org context requires going back to Home, switching the header selector, and re-entering Settings.

Organisation tab — compare projects

The Organisation tab is for comparing projects across the org over a time range.

Filters

Filter	Behaviour
Project (multi-select)	Narrow which projects feed the charts. "All projects" uses every project returned for the org.
Date range	Default range is the last 30 days (inclusive).

The three charts

Three bar-chart cards sit side-by-side. Each bar is a project; values are aggregated for the selected date range and project filter.

Card	What it measures
Swifter adoption	Share of pull requests closed through Swifter out of all closed PRs in the period. Shows how much merged work went through Swifter versus other paths. Higher usually means more delivery runs via the platform.
Automation rate	Among PRs created through Swifter, the average share of code contributed by the agent inside each PR (versus human edits in the same PR). Higher means more automation in that slice of work.
Manual intervention rate	Average share of follow-up user prompts among user messages only in agent chat across work items in the period. Agent replies are not counted; short answers to the agent's questions are not counted as follow-ups. Higher means more of the user's own text was steering; lower usually means more short / question-style replies.

Drill-down

Click a project's bar to open the Projects view for that project — same organisation — so you can inspect time-based detail and the work-items table below.

Projects tab — one project, time trend

The Projects tab is for looking at a single project's behaviour over time.

Filters

Filter	Behaviour
Project selector	Pick a project, or choose the option that returns you to the organisation-wide view.
Date range	Default is the last 7 days.
Granularity	How bars are grouped in time — Daily, Weekly, Bi-weekly, Monthly, or Quarterly.

The three charts — time-series

Each bar is a period in your range, so trends across the window are visible.

Card	What it measures
Swifter adoption	Same meaning as on the Organisation tab, but per time bucket — so you can see whether use of Swifter for merges goes up or down. Higher bars point to more Swifter-mediated delivery in that window.
Automation rate	Same meaning as on the Organisation tab, per time bucket: how much of the code in Swifter-created PRs is agent-written in each period. Higher means more agent contribution in that interval.
Code churn	Share of lines rewritten within a PR across different commits, per time bucket. Captures rework on the same lines before merge. Lower usually means fewer round-trips on the same edits; higher can mean more iteration or refactors across commits.

Work-items table

Below the charts. Each row is a work item, with columns:

Column	Source
ID	Click to open the work item.
Title	Work item title.
Assignee	The named owner.
Status	Lifecycle status.
PR	Linked pull request.
Automation rate %	From the linked merged PR. Same meaning as the Automation rate chart. Higher is usually "better". Blank when no data.
Code churn %	From the linked merged PR. Same meaning as the Code churn chart. Lower is usually "better". Blank when no data.
Manual intervention %	For this item's chat only — same definition as the Manual intervention rate card on the Organisation tab. User messages only; follow-ups vs short replies. Blank when no data.

Status, people, and date filters above the table adjust the rows shown on the page.

How the Dashboard connects to the rest of the blueprint

Use case	Where to go
Understand what each metric means in detail	Monitoring — Swifter Adoption and the per-metric sections that follow.
Decide what to do when the numbers move	Monitoring — Weekly review cadence and the joint-interpretation playbook.
Pull a specific work item's history for diagnosis	Click the ID in the work-items table; the work-item page opens with chat history and Dev / App / Test tabs.
Set baseline expectations at engagement start	Monitoring — Baseline metrics.

The Dashboard is the visible reporting surface; the operating definitions and decision rules live under Monitoring.