> 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-ctools/10.2-ctools/cde-quick-start-guide/open-cde-ctools-cde-quick-start.md).

# Open CDE

You can launch the dashboard editor from the Pentaho User Console Home page.

1. Log on to the Pentaho User Console.
   1. Launch a Web browser and enter the URL of the Pentaho Server.

      The page loads an introductory screen with a **Login** section.
   2. Enter your user name and password and click **Login**.

      ![Pentaho User Console Login](/files/5Ywyy4R8c3sP4mzI1uMk)

      You are now logged into the User Console and ready to start creating and running reports and dashboards.
2. From the Home page, click the **Create New** button.
3. From the menu that displays, select the **CDE Dashboard** option.

   You can now begin creating your first CDE dashboard. Alternatively, you can click the **File** menu, click **New**, and then click **CDE Dashboard**.

   ![Menu of new reports to create on PUC](/files/ZNpgKKWSNviccFDPtktm)

The dashboard editor now displays in a new tab on the Home page, showing a blank dashboard. You are now ready to create your first 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-ctools/10.2-ctools/cde-quick-start-guide/open-cde-ctools-cde-quick-start.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.