> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/introduction-to-inforiver/get-started/installing-inforiver-for-yourself.md).
# Installing Inforiver for yourself
This section outlines the steps involved in installing the Inforiver visual for yourself.
1. Open your report in Power BI Desktop or Power BI service.
2. Select the ellipsis from the visualizations pane.
3\. Select **Import a visual from a file** from the menu.
4\. If you get a message cautioning you about importing custom files, select **Import.**
5. Navigate to the folder that has the custom visual file (.pbiviz) and open it.
6. When the visual has successfully been imported, select **OK**.
7. The visual now appears as a new icon in the visualizations pane of the current report.
8\. If you want the visual to remain on the visualization pane for all reports right-click on it and select **Pin to visualizations pane**.
9. The visual gets pinned.
In the next section, we'll look at how an admin can install Inforiver for the organization.
---
# 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.inforiver.com/introduction-to-inforiver/get-started/installing-inforiver-for-yourself.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.
