> 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/customer-management/b2b-roles-and-approval-process.md).

# B2B Roles & Approval Process

For business customers, the connector assigns a **role** to each contact. It controls what the respective B2B user is allowed to do in the shop.

**The three roles at a glance**

| Role         | View | Order | Approve |
| ------------ | :--: | :---: | :-----: |
| **View**     |   ✓  |   –   |    –    |
| **Orderer**  |   ✓  |   ✓   |    –    |
| **Approval** |   ✓  |   ✓   |    ✓    |

* **View:** May see the assortment and prices and forward a shopping cart for approval – but may not place a binding order.
* **Orderer:** May view and create orders.
* **Approval:** May additionally approve orders (for example, approve purchases made by colleagues).

**Typical approval process**

```mermaid
flowchart LR
    A[View/Orderer creates a shopping cart] --> B{Approval required?}
    B -->|yes| C[Approval user reviews]
    C -->|approved| D[Order is placed]
    C -->|rejected| E[back to the creator]
    B -->|no| D
    D --> F[Order intake in BC]
```

The order that is placed reaches Business Central through the regular [order intake](/shopware/shopware6_en_us/order-processing/order-intake-from-shopware-into-bc.md).

**Setup**

1. Enter the role IDs in the configuration (**B2B Contacts** area).
2. Assign the appropriate role to the contacts.
3. Upload the contacts as B2B users.

{% hint style="info" %}
The approval workflows themselves are displayed within the Shopware B2B environment. The connector ensures that the correct users are created in the company account with the correct role.
{% endhint %}

{% hint style="success" %}
**Recommendation:** Assign the **Approval** role sparingly and deliberately – ideally to buyers or managers who are responsible for orders.
{% 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 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/customer-management/b2b-roles-and-approval-process.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.