> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/analytics/dashboard-widgets.md).

# Dashboard Widgets

### Overview

Widgets are the building blocks of dashboards.

Each widget represents a metric, chart, or summary view.

### Key Concepts

* **Widget**: visual representation of a metric or breakdown
* **Metric**: computed value, such as counts by status
* **Dimension**: grouping field, such as Segment, Process, or owner
* **Filter**: constraint applied at dashboard or widget level

### How It’s Used

Use a small set of widgets for weekly governance.

Use drill-down widgets to convert dashboard signals into follow-up work lists.

### Benefits

* Faster reviews through high-signal visuals
* Consistent reporting across Projects
* Better early warning for blockers and overdue work

### Setup Steps

{% stepper %}
{% step %}

### Select a metric

Choose a metric aligned to the review purpose, such as open work by status.
{% endstep %}

{% step %}

### Select dimensions and filters

Group by a consistent dimension, such as Segment Type, Process, or owner.
{% endstep %}

{% step %}

### Validate scope and definitions

Validate that widget scope matches the intended Organization and Project set.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep widget definitions stable across reporting cycles.
* Avoid mixing unrelated audiences in one dashboard.
* Use filters consistently across dashboards to support comparability.

### Summary

Widgets translate Project data into reviewable governance signals.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/analytics/dashboard-widgets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.