# Groups

1. [Home](https://www.agilicus.com/)
2. [Agilicus AnyX Administrative Web Interface](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/)
3. [Access](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/access/)
4. Groups

![](https://www.agilicus.com/www/203fb27a-featured-anyx-admin-accessgroups.png)## Groups

[CONTACT](/contact-us/)

The **Groups** page (route `/group-admin`) lists the groups in your organisation and is where you create them, add members, and set up group email addresses.

![Groups overview](https://www.agilicus.com/www/82d35de1-groups-overview.png)    ## Purpose

Groups behave as users for assigning permissions, and they can nest. The Groups page is the place to create one group per role or team, add the people who belong to it, and then use the group everywhere a single user could be granted access. When a group receives a permission, every member of the group receives it, which keeps access management consistent and auditable.

## Why use it

- Grant access in bulk: assign a permission to a group instead of to each user individually (see [Policies and permissions](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/policies-and-permissions/)).
- Mirror your organisation's roles and your identity provider's group structure.
- Nest groups: a group can contain other groups, so you can build a hierarchy such as *all staff* containing *engineering* and *finance*.
- Give a group an email address that forwards to its members, useful for team mailing lists.

## When to use it

- During initial setup, to create the role groups you will grant permissions to.
- When onboarding new people: add them to the relevant groups rather than granting permissions one by one.
- When you need a team alias address, or when your identity provider supplies upstream groups that you map into portal groups (see [Custom identity](/anyx-guide/agilicus-anyx-administrative-web-interface/authentication/custom-identity/) and [Onsite identity](/anyx-guide/agilicus-anyx-administrative-web-interface/authentication/onsite-identity/)).

**Prerequisite**: permission to administer groups (an owner or administrator role).

## How to use it

1. Open **Access > Groups** from the left navigation.
2. Review the table. Each row is a group with its name, description, member chips, and labels.

![Groups overview](https://www.agilicus.com/www/82d35de1-groups-overview.png)    ### Creating a group

1. Select **ADD GROUP**. A new empty row appears at the top of the table.

![New group row](https://www.agilicus.com/www/e76eb19f-groups-add-group.png)    1. Type the group **Name** (the only required field). Optionally add a **Description**.
2. To add members, click into the **Users** chips column and start typing. The autocomplete lists matching users; select one to add it as a chip. Repeat for every member.
3. Click outside the row to save. The group is created asynchronously and the table reloads.

### Editing a group

The name and description cells are editable in place. Members are managed through the **Users** chips column or the advanced configuration dialog.

### Managing group members

Select the **more** menu on a group's row, then choose **Configure Users**. The dialog shows a transfer list: **Available Users** on the left and **Current Users** on the right.

![Configure Users dialog](https://www.agilicus.com/www/c3604a95-groups-configure-users-dialog.png)    Tick users in either table and use the transfer button to move them to the opposite table.

![Configure Users after moving a member](https://www.agilicus.com/www/c3604a95-groups-configure-users-moved.png)    Select **UNDO** to revert the changes, or **CLOSE** to finish. The updated membership then applies asynchronously.

### Other row actions

- **Copy Group Email** copies the group's email address to the clipboard.
- **Configure Labels** opens the same transfer-list pattern for the group's labels.

## Fields and controls reference

| Control | Purpose | Required | Default | Valid values | Notes |
|---|---|---|---|---|---|
| Name | The group's name | Yes | n/a | Any text | Unique per organisation |
| Description | Free-form note about the group | No | n/a | Any text |  |
| Users | The members of the group (users or nested groups) | No | n/a | Users and groups | Chips column with autocomplete |
| ADD GROUP | Adds a new editable row | n/a | n/a | n/a | Saved when it passes validation |
| DELETE GROUPS | Deletes the selected groups | n/a | n/a | n/a | Bulk action on ticked rows |
| UPLOAD GROUPS | Imports groups from CSV | n/a | n/a | CSV |  |
| DOWNLOAD GROUPS | Exports the group list as CSV | n/a | n/a | n/a |  |

## Dialogs and popups

- **Configure Users**: the transfer-list dialog described above for managing group membership.
- **Configure Labels**: the same transfer-list pattern applied to labels.
- **Upload groups from CSV (csv-edit-dialog)**: the **UPLOAD GROUPS** button reads a CSV file and opens the table editor where you can fix headers and rows before saving. Missing required headers (for example `first_name`) are highlighted, and you can map or ignore columns, delete rows, undo edits, or download the table as CSV.

![Groups CSV edit dialog](https://www.agilicus.com/www/82d35de1-groups-csv-edit-dialog.png)    - **Confirmation dialogs**: deleting groups confirms before acting.

## Configuration versus diagnostics versus confirmation

- **Configuration**: group names, descriptions, members, and labels.
- **Diagnostics**: none on this screen; the group email and membership are configuration.
- **Confirmation**: deleting a group is permanent and removes its membership and any direct assignments made to the group.

## Pagination and async behaviour

- The table pages at **25 rows per page**.
- Group changes apply asynchronously. After creating a group, adding members, or editing the name, wait a few seconds and reload to confirm. Permission changes made through a group propagate to all members.

## Troubleshooting

- **A member does not appear after adding them**: wait for the asynchronous update and reload. Confirm the member exists as a user in the organisation.
- **The autocomplete shows no users**: the search matches users by display name and email; check the spelling, or add the user first on the [Users](/anyx-guide/agilicus-anyx-administrative-web-interface/access/users/) page.
- **A group cannot be deleted**: confirm the row is ticked and that you have permission to administer groups.

## See also

- [Policies and permissions](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/policies-and-permissions/)
- [Users](/anyx-guide/agilicus-anyx-administrative-web-interface/access/users/)
- [Resource groups](/anyx-guide/agilicus-anyx-administrative-web-interface/access/resource-groups/)
- [Service accounts](/anyx-guide/agilicus-anyx-administrative-web-interface/access/service-accounts/)
- [Application permissions](/anyx-guide/agilicus-anyx-administrative-web-interface/access/application-permissions/)
- [Resource permissions](/anyx-guide/agilicus-anyx-administrative-web-interface/access/resource-permissions/)
- [Custom identity](/anyx-guide/agilicus-anyx-administrative-web-interface/authentication/custom-identity/)
- [Labels](/anyx-guide/agilicus-anyx-administrative-web-interface/organisation/labels/)

## Web guide

- [Groups](https://www.agilicus.com/product-guide/groups)
- [When should I use a group?](https://www.agilicus.com/when-should-i-use-a-group)
- [Using groups for assigning role-based permissions](https://www.agilicus.com/using-groups-for-assigning-role-based-permissions)