> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/vendor-platform/customer-accounts/user-groups.md).

# User Groups

User groups allow you to organize license users into named groups for easier management across your account.

User groups can be managed at two levels:

* **License Users: N**avigate to **License Users → User groups** to manage groups across all license users globally

<figure><img src="/files/YBXajCHDk8ewe1PpUSfi" alt=""><figcaption></figcaption></figure>

* **Customer Account: O**pen a specific Customer Account and navigate to the **User groups** tab to manage groups within that account

<figure><img src="/files/wsyWJZiiEizgeZZFbuHF" alt=""><figcaption></figcaption></figure>

### Creating a User Group

Click **Add user group** and fill in the following fields:

<figure><img src="/files/qthy44YBt4g25zipNhSt" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/KKA1CUfkKEyun2ko7fjf" alt=""><figcaption></figcaption></figure>

* **Code: U**nique identifier for the group
* **Name:** Display name of the group
* **Description:** Optional description
* **Metadata JSON:** Optional metadata in JSON format

Click **Confirm** to save the group.

### Managing a User Group

Once a group is created, open it to view its details and manage its members. Each group displays the following information:

<figure><img src="/files/R27kHV3OERLkh2SwPwbE" alt=""><figcaption></figcaption></figure>

* **Name:** Display name of the group
* **Code:** Unique identifier
* **Description**: Optional description
* **Customer accoun:** The customer account this group is associated with
* **Metadata:** Any metadata attached to the group

You can edit the group details at any time using the **Edit user group** button, or remove the group using the **Delete** button.

<figure><img src="/files/667OQG9SqWOvLnYgXHLw" alt=""><figcaption></figcaption></figure>

### Adding Users

Navigate to the **Users** tab within the group and click **Add user** to assign license users to the group. Users are listed with their email, first name, last name, and phone number.

<figure><img src="/files/eRXA0sVBeZnVYxrldale" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ZN9fiOX027wA4UTRS51u" alt=""><figcaption></figcaption></figure>

### Adding Licenses

Navigate to the **Licenses** tab within the group and click **Add license** to assign licenses to the group. You can search and filter licenses by standard fields and metadata filters.

<figure><img src="/files/pDc1umgGhA1VTZQFJfAs" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/GYpuXLRB3G090EbzPq5G" alt=""><figcaption></figcaption></figure>

### Adding License Managers

Navigate to the **License managers** tab within the group and click **Add manager** to assign a license manager to the group.<br>

<figure><img src="/files/uhbhlfXe8ph39CEWolLf" alt=""><figcaption></figcaption></figure>

&#x20;Fill in the following fields:

<figure><img src="/files/iA9AAuOWu5qz0CkNc41V" alt=""><figcaption></figcaption></figure>

* **Email**
* **First Name**
* **Last Name**
* **Phone Number**
* **Metadata JSON**

Click **Confirm** to save.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.licensespring.com/vendor-platform/customer-accounts/user-groups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
