> 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/troubleshooting-and-support/common-questions.md).

# Common questions

Answers about search, opening documents, and archive registration.

## The posted document is not in the archive

That is expected in this version. Business Central only registers the document. The PDF is not uploaded. You can search for documents that are already stored in the Inoxision archive.

## The action is missing

Check the **SOU BC Inoxision** permission set. The queue needs **SOU BC Inoxision Admin**. **Search Inoxision** is on customers, vendors, and the four posted document types, not on quotes or orders.

## The connection check fails

Check the HTTPS address, that **API Key Stored** is Yes, and that **Auth Mode** is **Authorization Bearer**. **Allow Non-HTTPS** does not work in a production company.

## A result does not open

The document link must use HTTPS, and its host must be allowed. Update **Allowed Document Hosts** when the link uses a different host from the connector address.

## The API key is missing in another company

The key is stored per company. Enter it again in the second company.


---

# 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.solutioo.de/inoxision-archiv-connector/inoxisionarchivconnector_en_us/troubleshooting-and-support/common-questions.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.