Groups
What this screen is for
Groups organise users into teams. A group has members and a member count, and is what components and projects are owned by. Groups are about organisation and ownership; they are not how permissions are granted — that is Roles.
Before you start
| To do this | You need |
|---|---|
| See the tab | platform-settings.group.read |
| Open a group’s details | platform-settings.group.view-details |
| Create a group | platform-settings.group.create |
| Rename or edit a group | platform-settings.group.update |
| Delete a group | platform-settings.group.delete |
| Add or remove members | platform-settings.user.assign-group |
Note that membership is governed by a user permission, not a group one. It
is possible to hold group.update and still be unable to change who is in it.
Opening it
- Settings › People & Access
- Select the Groups tab.
The interface
📸 Screenshot Placeholder: The Groups tab with several groups listed. Mark: (1) the Add Group button, (2) the search field, (3) the member count on a row, (4) the row action icons.
| # | Control | What it does | When you’d use it |
|---|---|---|---|
| 1 | Add Group | Opens the creation dialog | Setting up a new team |
| 2 | Search | Filters by group name | Larger installs |
| 3 | Member count | How many users are in the group | Spotting empty groups |
| 4 | Row actions | View details, edit, delete | Managing an existing group |
An empty state is shown when no groups exist yet, with a direct call to create the first one.
Walkthroughs
Create a group
Requires platform-settings.group.create.
- Settings › People & Access › Groups.
- Click Add Group.
- Give it a name that matches how the organisation actually talks about the team — it will appear as the owner on catalog entities.
- Save.
Add members
Requires platform-settings.user.assign-group.
- Open the group.
- Add the users. The member count updates once the group details reload.
Delete a group
Requires platform-settings.group.delete.
- Find the group and click delete.
- Confirm.
Check first whether anything is owned by that group. Deleting it does not delete its members, but it can leave components without an owner, which shows up later as gaps in the catalog rather than as an error here.
Scenario
A team splits in two. Platform Engineering has grown and is separating into Platform and Observability.
- Create the Observability group.
- Move the relevant members across — add them to the new group first, then remove them from the old one. Doing it in that order means nobody is ownerless in between.
- Reassign the components that Observability now owns.
- Check the member counts on both groups; a count of zero on the original group means you moved everyone and should delete it rather than leave it behind.
Note that this changes ownership and organisation only. If the new team needs different access, that is a role change and is separate work.
When it doesn’t work
| Symptom | Cause | How to check | Fix |
|---|---|---|---|
| Cannot add a member although you can edit the group | Membership needs platform-settings.user.assign-group, not a group permission |
Access Explorer for yourself | Ask for a role granting user.assign-group |
| Member count looks wrong after a change | Counts are fetched per group and refresh when details reload | Reopen the group | Reload the page |
| Group created, but nothing changed for its members | Groups do not grant permissions | — | Assign a role; groups are ownership, not access |
| Cannot open a group’s details | Missing platform-settings.group.view-details |
Access Explorer | Ask for a role granting it |