> 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/pentaho-user-console.md).

# Pentaho User Console

The Pentaho User Console (PUC) is a web-based design environment where you can analyze data, create interactive reports, dashboard reports, and build integrated dashboards to share business intelligence solutions with others in your organization and on the internet. In addition to its design features, the Pentaho User Console offers a wide variety of system administration features for configuring the Pentaho Server.

* [Log in to the Pentaho User Console](https://docs.pentaho.com/pba/pentaho-user-console/log-in-to-the-pentaho-user-console.md)

  Get started by logging into PUC.
* [Modern Design](https://docs.pentaho.com/pba/pentaho-user-console/modern-design.md)

  The Modern Design interface for the Pentaho User Console (PUC) offers an improved user experience that is intuitive, responsive, and secure. Additionally, the following components are exclusively available in the Modern Design interface: Plugin Manager, Semantic Model Editor, and Pipeline Designer.&#x20;
* [Classic Design](https://docs.pentaho.com/pba/pentaho-user-console/classic-design.md)

  The Classic Design interface for the Pentaho User Console (PUC) includes perspectives and additional features, such as themes and access to the Data Source Wizard and Data Source.


---

# 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/pentaho-user-console.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.
