> 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-interactive-reports-cp/read-and-export-in-view-only-mode.md).

# Read and export in view-only mode

After you save your Interactive Reports, browse for it in your Pentaho repository. You can quickly identify Interactive Reports by their icon. When the report appears, notice that the toolbar that allows you to perform certain actions on the report.

![Interactive Report View Only Toolbar](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-e898f5432346e804f10cf60916377557efb0da79%2FPIR_ViewOnlyToolbar.png?alt=media)

Hover your mouse over the icons in the toolbar to see which actions you can take. These actions include:

* Exporting a report as a PDF, HTML, CSV, Excel Workbook, or Excel 93 - 2003 Workbook file to be saved locally.
  * You can also export a report in **Edit** mode.
* Adding filters for viewing report data.
* Rearranging the report layout, such as moving, sorting, and removing columns from the report.

You cannot save any changes to your report when you are in **View-only** mode. However, you can click **Edit** in the User Console toolbar to return to edit mode and save your changes.


---

# 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-interactive-reports-cp/read-and-export-in-view-only-mode.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.