> 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/editable/get-started/editable-pre-requisites.md).

# EDITable Pre-requisites

Before you set up EDITable, you must complete the following additional steps with your Power BI administrator:

* EDITable is an add-on visual that operates on top of the Power BI framework, so users must log in with their Microsoft O365 account. Learn more more about Admin consent for Editable's Entra ID.
* Network firewalls block connections from IP addresses that do not have permission. You need to whitelist EDITable's outbound IPs in your Azure SQL database firewall rules.
* EDITable connects to data sources only through DirectQuery. Please ensure to select **DirectQuery** in Data Connectivity mode when you are connecting to data. To learn more, you can check out these pages: [About DirectQuery in PowerBI](https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-about) and [Connect using DirectQuery](https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-use-directquery).


---

# 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/editable/get-started/editable-pre-requisites.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.