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

# Create a dashboard

You must be logged into the User Console. Use these steps to create a new dashboard.

1. From the User Console Home page, click **Create New**, then select **Dashboard**.

   The name you entered appears on the top left corner of the dashboard. This name helps you identify the page if you want to edit, copy, or delete it later.
2. On the bottom of the page, click the **Properties** tab, and enter a title for your dashboard page in the **Page Title** text box.
3. Click **Templates** to choose a dashboard layout.

   A blank dashboard with the layout you selected appears.
4. Click **Theme** to choose a theme for your dashboard.

   The theme you selected is applied to your dashboard.

You now have the basic framework for a Pentaho dashboard.


---

# 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://docs.pentaho.com/pba/10.2-analytics/pentaho-dashboard-designer-cp/creating-dashboards/create-a-dashboard.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.