Configure dashboards

Curate the dashboard widgets available across the organization, set sensible defaults so dashboards start useful, and let project context shape what each project offers.

The dashboards admin area governs the dashboard experience across the organization — which widgets are available, what’s enabled, and the defaults people start from. Curate it well and everyone builds from a relevant palette onto a useful starting point; leave it sprawling and every dashboard is a blank slate over too many options. For the reference, see Dashboards.

Curate the available widgets

The widget set people can choose from is something you decide, not a fixed list.

Before you start Open Administration and go to Dashboards. You'll need administrator access.

  1. Choose which widgets are available and enable them broadly.
  2. Curate the set so people build from a relevant, supported palette rather than a sprawling list.

Result A focused widget palette that reflects how your organization actually works. See Dashboards.

Set sensible defaults

Defaults decide what a new dashboard looks like before anyone customizes it.

  1. Set the defaults so a new dashboard starts useful rather than blank.
  2. Use reset to defaults to bring a configuration that has drifted back to a known-good state.

Result People begin from a dashboard that's already worth looking at, with less setup for everyone.

Let project context shape it

Dashboard configuration takes project context into account, so what’s offered fits the work.

  1. Configure widgets and defaults with project context in mind, so they reflect what's appropriate for the work in a given project.
  2. Keep it coherent — a project that doesn't use a module shouldn't be offering that module's widgets.

Result Each project's dashboards offer what's relevant to it, and nothing that isn't.

Note Good defaults here pay off everywhere: less setup for each person, and a more consistent view of the program across teams. Curate deliberately rather than exposing every widget — a smaller, well-chosen palette is more useful than an exhaustive one.

Where to go next

With the building blocks in place, people assemble and read their own dashboards as described in Configuring dashboards & widgets. For the program-level view those defaults feed, see Coverage, quality & compliance.

Was this helpful?