> 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/log-in-to-the-pentaho-user-console.md).

# Log in to the Pentaho User Console

Get started with the User Console by following these steps to log in:

1. Launch a Web browser and enter the URL of the Pentaho Server.

   The Welcome page appears.

   ![Welcome page](https://1610525749-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdbSFXbJFiObHB299lSSa%2Fuploads%2Fgit-blob-683e2620184cc5f3f8ad2ac76d6e3ca676346f71%2FPUC_Welcome_page.png?alt=media)
2. Enter your user name and password and click **Log in**.

   The Home perspective appears.

   You are now logged in to the User Console and ready to start creating and running reports and dashboards.


---

# 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/log-in-to-the-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.