---
title: Groups
id: "en:accounts:ROOT:groups.adoc"
site: en
component: accounts
module: ROOT
version: 3.0
lang: en
url: "https://help.rtlscloud.io/en/accounts/3.0/groups.html"
source_repo: "https://github.com/iot-invent/xCloud.git@3.0.x"
source_path: accounts/docs/en/modules/ROOT/pages/groups.adoc
---

# Groups

A group collects users so that a role can be granted once for the group instead of once per person. Whoever joins the group later has the group’s permissions without any permission being touched.

Groups belong to the tenant and are the same across all of its spaces.

## Group list

![Groups](_images/view/groups.webp)

### Action bar

| Action | Description |
| --- | --- |
| ![refresh](_images/refresh.svg) **Refresh** | Reloads the list of groups. |
| ![plus](_images/plus.svg) **Add** | Opens the dialog for creating a new group. |
| ![edit](_images/edit.svg) **Edit** | Adjusts the name, the description and **Active** of the selected group. Members are not managed here — see the note above. |
| ![delete](_images/delete.svg) **Delete** | Removes the selected group. The users remain; they lose the permissions they had through this group. |
| ![menu](_images/menu.svg) **More options** | Gives access to further group functions. |

### Columns

| Column | Description |
| --- | --- |
| **Name** | The name of the group. The arrow indicates which column the list is sorted by. |
| **Description** | Free text describing the purpose of the group. |
| **Active** | An `X` marks an active group. |

> **TIP:** Meaningful names pay off in the permission list — only the group’s name appears there, without its description.

## How groups work

Three points that the user interface does not reveal on its own:

**Groups are flat.** A group has a name, a description and the **Active** switch — no parent. There is no group inside a group, and therefore no inherited membership.

**Membership sits on the user.** It is a property of the user account, not of the group. The same assignment can therefore be maintained from either side: on the user through the **Groups** tab, or on the group through the **Users** tab.

> **NOTE:** The Users tab only appears when the group is opened — by double-clicking the row, or through the read view. It is not in the edit dialog; that one holds only the name, the description and Active. Whoever looks for members and opens the edit dialog will not find them.

**Roles are not maintained on the group.** A group carries no permissions. It receives a role the way a user does: as an entry in the permission list of the object the role applies to — the tenant or a space. In that list the group then appears as the **identity** instead of a person, see [Permissions](permissions.md) and [Roles](roles.md).

A group can also be granted while inviting a user, instead of a role: after accepting, the invited person is a member and has the group’s permissions, see [Users](users.md).