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

# Dashboard Designer

Templated Interactive, Analyzer & Report Designer Reports together with Queries & URLs ..

{% hint style="info" %}
Creating a dashboard in Dashboard Designer is as simple as selecting a layout template, theme, and the content you want to display. In addition to displaying content generated from action sequences, Interactive Reporting, and Analyzer, Dashboard Designer can also include:

• **Charts**: simple bar, line, area, pie, and dial charts created with Chart Designer.

• **Data Tables**: tabular data.

• **URLs**: Web sites that you want to display in a dashboard panel.
{% endhint %}

{% embed url="<https://www.loom.com/share/b7a6f8dbfa734c839cb1452d0905f2c7?hideEmbedTopBar=true&hide_owner=true&hide_share=true&hide_title=true>" %}
Dashboard Designer
{% endembed %}

{% hint style="info" %}
Dashboard Designer also has dynamic filter controls, which enables end-users to change a dashboard's details by selecting different values from a drop-down list, and to control the content in one dashboard panel by changing the options in another (content linking).
{% endhint %}

<figure><img src="https://content.gitbook.com/content/iyGCAvfJ7v68TnXf8icC/blobs/GbVey5nddT5CWGPDFSff/image.png" alt=""><figcaption><p>Dashboard Designer</p></figcaption></figure>


---

# 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://academy.pentaho.com/pentaho-business-analytics/business-analytics/dashboard-designer.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.