> For the complete documentation index, see [llms.txt](https://docs.3q.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3q.video/user-guide-new-ui/account/groups.md).

# Groups

{% hint style="info" %}
**Availability note:** The **Groups** feature is not available for all accounts (tenants). We recommend to use this feature only in complex environments. If groups are not activated you can apply access to projects (content pools) direct to users.
{% endhint %}

Groups are used to structure access to projects (**content pools**) and users within an account. They provide an additional layer of access control by linking projects to groups and assigning users with specific roles to those groups.

<figure><img src="https://949886435-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FY0a9tRqzqI1wGBkmcjxd%2Fuploads%2FDNBw1Ox4dfApZDXP9zmS%2FBildschirmfoto%202026-01-26%20um%2011.58.17.png?alt=media&amp;token=2cb03d50-3138-41b3-94ac-1052961ad842" alt=""><figcaption></figcaption></figure>

#### Purpose of Groups

Groups allow you to:

* Link **projects (content pools)** to a groups
* Grant **group-based access** to users
* Assign **different roles** to users per group

Access to a project is determined by the user’s role within the group the project is assigned to.

#### Typical Use Cases

Groups are commonly used to:

* Separate content by department, team, or audience
* Restrict access to specific projects
* Manage permissions at scale without assigning rights per project

If Groups are not enabled for your account, access control is handled without group-based assignments.

### Access and Availability

* Groups are available at the **account level**
* Only users with appropriate permissions can access group management