Concepts

Project sections: Overview, Plan, Deliver, Assure, Reports, Settings

Open a project and a row of six sections runs across the top. They split everything a project holds into six places, in this order:

Overview · Plan · Deliver · Assure · Reports · Settings

Select one and you switch to that part of the project. The section you’re on is highlighted. A bare project link — one with no section after it — lands you on Overview, the project’s home screen.

This page is the map. For the wider tour of the app outside a project — the icon rail, the breadcrumb bar, the command palette — see Find your way around.

The two-tier layout

Three of the six sections hold a single screen. The other three split into two sub-features, which appear as a second row of choices directly under the section row once you select them.

SectionWhat’s inside
Overviewone screen — the project dashboard
PlanBlueprint + Requests
DeliverTasks + Pipeline
AssureGovernance + Assurance
Reportsone screen — the usage and metrics ledger
Settingsone screen — the project’s configuration

When you select Plan, Deliver, or Assure, you land on its first sub-feature and the second row lets you switch to the other one. Overview, Reports, and Settings have no second row — there’s just the one screen.

How this guide points you somewhere

Because three sections nest, the docs name a destination as section > sub-feature. So:

  • Deliver > Tasks — the Tasks sub-feature inside the Deliver section.
  • Deliver > Pipeline — the Pipeline sub-feature inside Deliver.
  • Plan > Blueprint, Plan > Requests — the two sub-features inside Plan.
  • Assure > Governance, Assure > Assurance — the two sub-features inside Assure.

A single-leaf section is named on its own — just Overview, Reports, or Settings.

Two labels worth pinning down

Two names sit where you might not expect them. Learn them once and the rest reads cleanly:

  • Reports (the top-level section) is the project’s usage and metrics ledger — completion, throughput, cost, and cycle time over the project’s history. It is not an audit trail. See Read your usage charts.
  • Governance (a sub-feature under Assure) is the delivery and audit report — the record of where gates caught issues before they shipped.

So the metrics live under Reports; the audit record lives under Assure > Governance.

Overview: the project dashboard

Overview is the first screen you see inside a project, and it’s a live dashboard — a glance that tells you where the project stands without clicking anywhere.

  • Headline tiles across the top: Completion, Gates caught, Avg / task, and Avg cycle. Each shows a dash () until there’s enough history to fill it in.
  • Status alerts when something needs attention — for example, No GitHub repository connected, or a notice that the project is pausing.
  • An Active run card that, while a task is running, shows the live run moving through its pipeline stages — its branch and the stage it’s currently on. With nothing running, the card reads Pipeline and invites you to start a task from Deliver > Tasks.
  • A short in-flight line when work is running, telling you how many tasks are in flight and how many are waiting, with a View queue link straight to the task list.
  • Up next and Recently shipped lists — what’s queued and what just landed.
  • Context cards down the side that summarize the Plan layer (Blueprint, Requests), Assurance (Governance, the regression set), and connected Integrations (GitHub, Slack, Jira), each a quick jump into that part of the project.

From Overview you can reach almost anywhere the project needs you. The rest of the sections are where you do the detailed work.

Where each section leads

  • Plan — what the project intends to build. Blueprint is the maintained spec; Requests are change threads not yet folded into it.
  • Deliver — the work itself. Tasks is the queue and history of runs; Pipeline is the staged route a run travels. See The pipeline: stages and gates.
  • Assure — delivery quality. Governance is the audit report; Assurance is where you run regression and security regression suites. See Assurance: regression and security regression suites.
  • Reports — the usage and metrics ledger for the project.
  • Settings — the project’s configuration, including who’s on it, connected services, and the project’s quality settings.

Anything that needs a decision from you across all your projects gathers in one place outside this section row — the Needs You inbox, the app’s home screen.