> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/core-commerce/customer-management/groups.md).
# Customer Groups
Group your B2B customers to allow the right access and scope.
Here you can find an overview of the customer groups feature and its benefits.
{% hint style="info" %}
Looking for API reference? Check out the [Customer Service API](/api-documentation/api-guides/companies-and-customers/client-management.md) reference.
{% endhint %}
### Purpose
B2B scenarios require applying more structure to the management of your end customers.\
With Customer Groups, you can easily manage your customers to ensure the right level of authorization and access is granted to the customers within a company (legal entity).
### Features
The Emporix customer groups functionality combines a set of features:
| Feature | Description |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Granular permission control** | As a seller, you can set different access levels within groups, ensuring the right people have the right permissions from their customers. |
| **Stronger data security** | Restricting access to relevant team members of the end customer minimizes the risk of unauthorized data breaches. |
| **Improved organizational management** | As a B2B seller, you have a tool to manage the end customers organizations on their behalf, ensuring the structured and controlled access to business-critical information. |
| **Self-service for end customers** | End customers can independently manage their organization and users without relying on your support teams. Reduced dependency on manual administrative approvals leads to quicker role assignments and modifications within the user management. |
### Overview
Predefined customer groups are automatically created for each legal entity in the system. They are legal entity aware, which means that you can easily administer the company-related permissions. You can manage the customer groups from the Management Dashboard which facilitates assigning the right access to the right group members.
{% hint style="info" %}
To disable automatic creation of the predefined groups, set `predefinedLegalEntityGroupsCreationDisabled` to `true` in [System Preferences](/user-guides/management-dashboard/settings/system-preferences.md).
{% endhint %}
{% hint style="info" %}
To learn more how to manage customer groups, see the [Customer Groups User Guide](/user-guides/management-dashboard/customer-management/customer-groups.md).
{% 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://developer.emporix.io/user-guides/core-commerce/customer-management/groups.md?ask=&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.
