Configuring dashboards & widgets

A dashboard is a configurable view onto your program, built from widgets. Rather than a fixed screen, it’s a canvas you assemble from the pieces that matter to you — so the dashboard answers your questions, not a generic set.

Adding widgets

You build a dashboard by adding widgets from a library. Each widget shows one slice of the picture — a coverage figure, a quality score, a compliance gauge, a workload list — and you search the library and drop in the ones you need. Adding and removing widgets is how you tune a dashboard to a particular audience or purpose.

Arranging the layout

Widgets sit in a layout you control, so you can put the things you check most often where you’ll see them first and group related signals together. The arrangement is part of the dashboard, so the view you set up is the view you return to.

Per module and across the program

Each module has its own dashboard focused on that area — the Requirements dashboard, the Tests dashboard, and so on — giving you a tailored view of one part of the work. Alongside these, cross-module dashboards aggregate signals across the whole program, so you can see the big picture without drilling into each module in turn. You choose the altitude: deep in one area, or the program at a glance.

Scoped to your project

A dashboard reflects your active project, so the numbers it shows are the numbers for the work you’re actually looking at. Switch projects and the dashboard re-scopes to that project’s data. The signals those widgets surface — coverage, quality, and compliance — are covered next in Coverage, quality & compliance.