
Resource groups
The Resource Groups page (route /resource-group-admin) collects resources into named groups so you can grant permissions to many resources at once.

Purpose
A resource group groups resources that are logically associated with one another, for example the multiple services that make up an application. The resource group can then be used for permission assignment, so that any resource that is part of the group automatically receives the same permission. This is essential when you manage many resources, such as a fleet of desktops or a set of applications, that should be managed together.
Why use it
- Reduce repetition: grant a permission to the group once instead of to each resource.
- Keep related resources in step: adding a resource to the group immediately gives it the group’s access level.
- Organise by purpose or location, for example engineering desktops, finance applications, or factory floor.
- Combine with labels and policies for fine-grained control (see Policies and permissions).
When to use it
- When you have more resources than you want to administer one at a time.
- When a set of resources should always have the same access level.
- When new resources are added regularly and should inherit access automatically.
Prerequisite: permission to administer resources and permissions (an owner or administrator role).
How to use it
- Open Access > Resource Groups from the left navigation.
- If no resource groups exist yet, the table is empty.

- Select ADD RESOURCE GROUP, type a Name for the group, and click outside the row to save.

Adding resources to the group
- Select the more menu on the group’s row, then choose Configure Resources. The dialog shows a transfer list: Available Resources on the left and Current Resources on the right. Each entry shows the resource name with its type in brackets, for example
hr(application).

- Tick resources in either table and use the transfer button to move them to the opposite table. Only resources you have permission to manage appear as available.

- Select UNDO to revert, or CLOSE to finish. Membership applies asynchronously.
Other row actions
- 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 resource group’s name | Yes | n/a | Any text | Must be a valid resource name |
| Resources | The resources in the group | No | n/a | One or more resources | Shown as chips with type suffixes |
| ADD RESOURCE GROUP | Adds a new editable row | n/a | n/a | n/a | |
| DELETE RESOURCE GROUPS | Deletes the selected groups | n/a | n/a | n/a | Bulk action on ticked rows |
| UPLOAD RESOURCE GROUPS | Imports groups from CSV | n/a | n/a | CSV | |
| DOWNLOAD RESOURCE GROUPS | Exports the group list as CSV | n/a | n/a | n/a |
Dialogs and popups
- Configure Resources: the transfer-list dialog described above. Available resources page at 10 per page when there are many.
- Configure Labels: the same transfer-list pattern applied to labels.
- Confirmation dialogs: deleting resource groups confirms before acting.
Configuration versus diagnostics versus confirmation
- Configuration: group names, resource membership, and labels.
- Diagnostics: none on this screen.
- Confirmation: deleting a resource group is permanent and removes the group’s resource membership. Removing a resource from a group does not remove permissions granted directly to that resource.
Pagination and async behaviour
- The main table pages at 25 rows per page. The Configure Resources dialog pages at 10 rows per page.
- Group changes apply asynchronously. After adding a group or changing its membership, wait a few seconds and reload to confirm. Permission behaviour updates as the change propagates.
Troubleshooting
- A resource is not listed as available: you may lack permission to manage it, or it may already belong to the group. Search the available list and check the resource type filters.
- The group does not apply permissions: confirm the group is used in a permission grant on the Resource permissions page, and that the resources are members of the group.