> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/inoxision-archiv-connector/inoxisionarchivconnector_en_us/getting-started/requirements.md).

# Requirements

Archive, Azure connector, and the permission sets you need.

* Microsoft Dynamics 365 Business Central
* An Inoxision archive that already contains the documents you want to find
* The HTTPS address and API key of the connector. The connector is hosted on Microsoft Azure. You do not set up Azure inside Business Central.
* Permission set **SOU BC Inoxision** to search
* Permission set **SOU BC Inoxision Admin** to maintain the connection, the API key, and the archive queue

{% hint style="warning" %}
The API key is stored per company. Enter the connection again in each additional company.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/inoxision-archiv-connector/inoxisionarchivconnector_en_us/getting-started/requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.