> 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/magento-2-api-connector/magento2_en_us/getting-started/installation-permissions-and-role-center.md).

# Installation, Permissions, and Role Center

The app is deployed like a standard Business Central extension by an administrator or partner.

### Verify Installation

1. Open **Extension Management**.
2. Search for **solutioo Magento2 API Connector**.
3. Check version and active status.
4. Test updates in a sandbox first.

### Permission Set

Assign **SouPermissionSet** to operators. It includes extensive modify and delete permissions on connector data and logs.

{% hint style="warning" %}
Assign only to required users. For read-only evaluation, consider a separate read permission set.
{% endhint %}

### Profile “Magento Shop Administrator”

The profile bundles items, categories, bundles, options, dashboard, configuration, Mapping Hub, MSI mapping, and logs.

1. Open **My Settings**.
2. Select the role **Magento Shop Administrator**.
3. Reload the home page.

### Responsibilities

* Administrator: Installation, access, reset, migration
* Functional configurator: Mappings, taxes, customers, inventory
* Catalog team: Items, categories, media
* Order processing: Dashboard and documents
* Support: Logs and recovery


---

# 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/magento-2-api-connector/magento2_en_us/getting-started/installation-permissions-and-role-center.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.
