> 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/shopware/shopware6_en_us/getting-started/user-roles-and-permissions.md).

# User Roles and Permissions

For administrators: Manage user roles and permissions for the Shopware 6 API Connector.

{% hint style="info" %}
The icon <i class="fa-screwdriver-wrench">:screwdriver-wrench:</i> marks those chapters of the documentation that are primarily relevant for administrators.
{% endhint %}

The Shopware 6 API Connector uses the standard permission system of Microsoft Dynamics 365 Business Central. Here you learn which permissions are required to use the connector.

## 1. Assigning permissions

When the Shopware 6 API Connector is installed, a permission set is created automatically:

> **SOUSHW PERM:** Full access to all Shopware functions

Assigning it to an individual user

* Enter *"Users"* in the Business Central search function and open the page.
* Select the desired user.
* Click "*Permission Sets".*
* Add *"SOUSHOPWAREAPICONNEC"*.

<div align="left"><figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/2soS9wFIxXcgu87gPnNV/Bildschirmfoto%202026-01-27%20um%2009.38.51.png" alt=""><figcaption></figcaption></figure> <figure><img src="https://content.gitbook.com/content/Pma4R4cytVXRDRO1gkpH/blobs/t4CdwSUoVqNy2BdjiY0i/Bildschirmfoto%202026-01-27%20um%2009.39.27.png" alt=""><figcaption></figcaption></figure></div>

## 2. Required basic permissions

In addition to the Shopware permission set, users need the following standard permissions:

<table><thead><tr><th width="184.93798828125">Area</th><th width="225.18212890625">Required permission</th></tr></thead><tbody><tr><td>Items</td><td>Read, Write</td></tr><tr><td>Customers</td><td>Read, Write</td></tr><tr><td>Sales Orders</td><td>Read, Write</td></tr><tr><td>Sales Invoices</td><td>Read</td></tr><tr><td>Sales Credit Memos</td><td>Read</td></tr><tr><td>Sales Shipments</td><td>Read</td></tr></tbody></table>

{% hint style="info" %}
For the PDF upload, users additionally need read permissions for "*Posted Sales Documents"*.
{% endhint %}

## 3. Recommended user roles

{% tabs %}
{% tab title="Administrator" %}

* Full access to all functions
* Can change the configuration
* Can manage the API connection
* Can edit mapping tables
  {% endtab %}

{% tab title="Standard user" %}

* Can synchronize items
* Can import orders
* Can update prices and inventory
* **No** changes to the configuration
  {% endtab %}

{% tab title="Read-only" %}

* Can view activity logs
* Can display the order overview
* **No** synchronization functions
  {% endtab %}
  {% endtabs %}

## 4. Shopware API permissions

Corresponding permissions must also be in place on the Shopware side:

{% tabs %}
{% tab title="With integration access" %}
The integration requires the following permissions:

* `product:read`, `product:write`
* `category:read`, `category:write`
* `media:read`, `media:write`
* `customer:read`
* `order:read`, `order:write`
* `solutioo_invoice_document:read`, `solutioo_invoice_document:write` (for the PDF module)
  {% endtab %}

{% tab title="With user access" %}
The admin user that is used should have full admin rights.

{% hint style="warning" %}
Restricted permissions in Shopware can lead to errors during synchronization!
{% endhint %}
{% endtab %}
{% endtabs %}


---

# 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/shopware/shopware6_en_us/getting-started/user-roles-and-permissions.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.