> 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/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](https://2636742124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWqPfT8L6hOx1irjNJoua%2Fuploads%2Fgit-blob-d36ad7045c31a6f0854f76cf8e973eb1599ac788%2FPUC_Login_Hitachi.png?alt=media)

      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](https://2636742124-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWqPfT8L6hOx1irjNJoua%2Fuploads%2Fgit-blob-e0cc70df423c4a0de4364414449441872e36f74e%2FFig29-createNewCDEDashboard.png?alt=media)

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

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

```
GET https://docs.pentaho.com/pba-ctools/cde-quick-start-guide/open-cde-ctools-cde-quick-start.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.
