> 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/9.3-analytics/pentaho-interactive-reports-cp.md). # Pentaho Interactive Reports The intuitive, drag-and-drop, browser-based design environment for Interactive Reports enables you to quickly add elements to your report and format them any way you like. You do not need any special expertise to use Interactive Reports. You can also display Interactive Reports in a [dashboard](/pba/9.3-analytics/pentaho-dashboard-designer-cp.md) in the User Console. Here is a list of the main Interactive Reports features. * Drag-and-drop report design * Font selection * Column resizing * Column sorting * Ability to rename column headers * Copy and paste functionality * Unlimited undo and redo functionality * Ability to output reports as HTML, PDF, CSV, Excel Workbook, or Excel 93-2003 Workbook files * Ability to display reports in a dashboard Before you can create Interactive Reports, you must have access to a data source. The data source for Interactive Reports is based on the Pentaho relational data model, also known as the metadata data model. This model enables the Pentaho system to present data in reports in meaningful business terms instead of in abstract terms. For example, a table referred to as **CUST\_TBLE or ORDR\_TBLE** in the data model can be presented in your report as **Customers and Orders**. --- # 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/9.3-analytics/pentaho-interactive-reports-cp.md?ask=&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.