> 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/creating-custom-dashboards.md).

# Creating Custom Dashboards

### Overview

Custom dashboards align reporting to an Organization’s governance cadence.

They reduce manual status preparation and improve consistency.

### Key Concepts

* **Dashboard**: curated set of widgets for a reporting purpose
* **Widget**: chart or metric backed by Project data
* **Filter**: constraint applied to focus a review

### How It’s Used

Create dashboards for recurring reviews, such as weekly governance.

Create separate dashboards when audiences differ, such as delivery vs executive.

### Benefits

* Consistent reporting without rebuilding views each week
* Faster stakeholder alignment on progress and risk
* Cleaner trend tracking through stable definitions

### Setup Steps

{% stepper %}
{% step %}

### Create a dashboard

1. Navigate to **Analytics** → **Dashboards**.
2. Select **Create dashboard**.
3. Name the dashboard based on review purpose.
   {% endstep %}

{% step %}

### Add widgets

1. Add a small set of widgets first.
2. Validate each widget matches the intended scope.
   {% endstep %}

{% step %}

### Apply filters

1. Apply filters for Segment, Process, System, or status when available.
2. Confirm filters update widgets consistently.
   {% endstep %}

{% step %}

### Share access

Share dashboard access based on role and scope.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep one baseline dashboard per line of business.
* Keep widget definitions stable to protect trend comparability.
* Pair dashboards with Save Views for follow-up actions.

### Summary

Custom dashboards standardize governance reporting and reduce recurring preparation work.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/analytics/creating-custom-dashboards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.