# 2025-07-23: B2B Customer Groups - Migration

## Overview

We have completed an update to the customer group and assignment structure in the IAM service for all tenants. This change brings greater clarity and flexibility to how users are organized and managed within each legal entity.

## What’s new

* For every legal entity, three new customer groups have been created: **Admin**, **Buyer**, and **Requester**.
* All users have been reassigned to the appropriate new groups based on their roles and legal entity relationships.
* Users without a specific legal entity have been assigned to a default customer group to ensure continued access.

These changes make it easier to manage user permissions and roles within your organization.

## Summary of changes

| Area                | Description                                                                         |
| ------------------- | ----------------------------------------------------------------------------------- |
| Customer Groups     | New Admin, Buyer, and Requester groups created for every legal entity.              |
| User Assignments    | Users reassigned to the correct new groups according to their roles.                |
| Fallback Assignment | Users without a legal entity assigned to the default customer group for continuity. |

## Known problems

There are no known problems.

## Documentation

For more information, see the following pages:

* [Groups](/ce/management-dashboard/customer-management/customer-groups.md)
* [Company Shared Orders and Customer Groups](/ce/customer-use-cases/scenarios-introduction/shared-orders.md)


---

# Agent Instructions: 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:

```
GET https://developer.emporix.io/changelog/archive/changelog-2025/2025-07-23-b2b-customer-groups-migration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.