> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/pentaho-business-analytics/business-analytics/user-console.md).

# User Console

Gateway to reporting plugins & Pentaho Server services ..

{% hint style="info" %}

#### Introduction

The Pentaho User Console is a web-based interface that serves as the main portal for business users to access and interact with Pentaho's business intelligence capabilities. It provides a centralized platform where users can view, schedule, and share reports, dashboards, and analytics content.

The console features role-based security controls, allowing administrators to manage user access and permissions. Users can navigate through organized folders of content, execute reports on demand, set up automated report distribution, and interact with dynamic dashboards.

The interface supports various content types including interactive reports, analysis views, and data visualizations, making it a key component of Pentaho's business intelligence suite for non-technical users to access and analyze business data.

In Pentaho 11 you have the option to switch to the new login screen which will redirect you to the new pentaho console.
{% endhint %}

**Pentaho 11**

<figure><img src="https://3159385628-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyGCAvfJ7v68TnXf8icC%2Fuploads%2FDzqccVsOMHjFobeiORX3%2Fimage.png?alt=media&amp;token=83908290-1257-46a2-9826-ee92cbcc286b" alt=""><figcaption><p>NEW - Pentaho User Login</p></figcaption></figure>

***

{% embed url="<https://www.loom.com/share/31b64ef6661c42f99c2dcdbd6328266a?hideEmbedTopBar=true&hide_owner=true&hide_share=true&hide_title=true>" %}
Pentaho 10 User Console
{% endembed %}


---

# 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://academy.pentaho.com/pentaho-business-analytics/business-analytics/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.