> 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/10.2-analytics/pentaho-user-console/additional-features/plugins.md).

# Plugins

You can activate several plugins in the Pentaho User Console.

* [Pentaho Analyzer](/pba/10.2-analytics/pentaho-analyzer-cp.md): Conceptualize your data, add query parameters and filters, drill-down links, and create visualizations.
* [Pentaho Interactive Reports](/pba/10.2-analytics/pentaho-interactive-reports-cp.md): Create simple and on-demand operational reports without depending on IT or report developers.
* [Pentaho Dashboard Designer](/pba/10.2-analytics/pentaho-dashboard-designer-cp.md): Create dashboards that help decision makers gain critical knowledge at a glance.

You can also use **Pentaho CTools** (a set of community-driven tools) to help you develop and define your data structure, which you can then use in 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/10.2-analytics/pentaho-user-console/additional-features/plugins.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.