> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/using-the-platform/settings/settings-groups.md).

# Groups

The **Groups** tab of the [Settings](/amie-advanced/using-the-platform/settings.md) screen shows the tree of groups in your [Space](/amie-advanced/introduction/how-your-space-is-organized.md) and is where you add a group. To reach it, select **Settings** in the sidebar, then the **Groups** tab.

## Why this screen matters

Groups decide who sees what. A handset belongs to the group whose enrollment ID it used; a user sees their own group and everything beneath it. Before handsets are connected, this tab is where you build the structure planned on [Planning your groups](/amie-advanced/planning-and-installation/planning-your-groups.md); afterwards it is where you check which group sits under which, and add a group when a new team or building needs one of its own.

## Before you start

The tab shows the groups you can see: your own group and every group beneath it. A user placed at the top of the tree sees the whole Space. The tab does not follow the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header.

Grayed out? **Add Group** and the **+** beside each group depend on your role. Requires the **Admin** or **Owner** role — see [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md).

## Screen layout

### Add Group

**Add Group** sits at the top right. It opens the **Add New Group** dialog with the topmost group you can see selected as the parent — see [Add a group](#add-a-group).

### The group tree

One row per group, indented beneath its parent. Each row shows the group's name in bold and, beneath it in smaller gray text, the path to it from the topmost group you can see — for example **Riverside Hospital / Clinical / NICU**. Groups at the same level are listed alphabetically. A group that has groups beneath it carries a chevron, and selecting anywhere on that row, including the chevron, folds or unfolds them. Every group starts unfolded.

Pointing at a row reveals two icons at its right: a blue **+**, which opens the **Add New Group** dialog with that group already chosen as the parent, and, on every group except the top of the tree, a red trash icon.

{% hint style="info" %}
Not yet available: deleting a group. The trash icon does nothing yet. \[GAP-groups-1]
{% endhint %}

The tab has no rename, no move, and no count of the handsets or users in a group. To see which handsets are in a group, select it in the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) and open the Devices [Inventory](/amie-advanced/using-the-platform/devices-inventory.md); for users, read the **Group** column on the [Users](/amie-advanced/using-the-platform/settings/settings-users.md) tab.

## Controls

| Control                  | What it does                                                                              |
| ------------------------ | ----------------------------------------------------------------------------------------- |
| **Add Group**            | Opens the **Add New Group** dialog, parent preselected as the top of the tree you can see |
| A row that has a chevron | Selecting it, anywhere including the chevron, folds or unfolds the groups beneath it      |
| **+** on a row           | Opens the **Add New Group** dialog with that group as the parent                          |
| Trash icon on a row      | Has no effect yet. \[GAP-groups-1]                                                        |

## Icons and indicators

| Icon or indicator                      | Meaning                                  | When it appears                                                          |
| -------------------------------------- | ---------------------------------------- | ------------------------------------------------------------------------ |
| Chevron pointing down / right          | The group's subgroups are shown / hidden | On groups that have subgroups                                            |
| Blue **+**                             | Add a group beneath this one             | When pointing at a row; grayed out for the **User** and **Viewer** roles |
| Red trash icon                         | Delete this group — not yet available    | When pointing at any row except the top of the tree                      |
| Blank space where the chevron would be | The group has no subgroups               | On groups with no subgroups                                              |

## Common tasks

### Add a group

Requires the **Admin** or **Owner** role.

{% stepper %}
{% step %}
Select **Add Group**, or point at the group that should be the parent and select its **+**. The **Add New Group** dialog opens.
{% endstep %}

{% step %}
Type a name under **Group Name**. It is required, up to 100 characters, and must contain at least one letter or digit. Two groups may have the same name; the path beneath each row in [the group tree](#the-group-tree) tells them apart, so choose names that read clearly in a path.
{% endstep %}

{% step %}
Check **Parent Group**. The list shows every group you can see as a path; the group you started from is preselected. Change it if the new group belongs elsewhere.
{% endstep %}

{% step %}
Select **Add Group** at the bottom of the dialog (**Cancel** or the **×** closes it without saving). The new group appears in the tree, unfolded beneath its parent, and in the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header. If it could not be created the dialog reads **Failed to add group. Please try again.**
{% endstep %}
{% endstepper %}

A new group is empty. Handsets join it through its enrollment ID — see [Group Details](/amie-advanced/using-the-platform/settings/settings-group-details.md) — and users are placed in it when they are added — see [Users](/amie-advanced/using-the-platform/settings/settings-users.md).

## What to look for

* A group you expect that is not in the tree. It is above your own group, or in another branch; the tab shows only your group and those beneath it. A user at the top of the tree sees every group.
* Two rows with the same name. Read the path beneath each. Renaming is not available in the console; contact Spectralink if one must change — see [Getting help](/amie-advanced/introduction/getting-help.md).
* A group created in the wrong place. It cannot be moved or deleted here. Create it again under the right parent, and leave the misplaced one empty; contact Spectralink to have it removed.
* A grayed **+** or **Add Group**. Your role is **User** or **Viewer** — see [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md).

## Metrics on this screen

None.

## Related

* [How your Space is organized](/amie-advanced/introduction/how-your-space-is-organized.md) — what groups are and how they nest
* [Planning your groups](/amie-advanced/planning-and-installation/planning-your-groups.md) — deciding the structure
* [Group Details](/amie-advanced/using-the-platform/settings/settings-group-details.md) — the enrollment ID for each group
* [Users](/amie-advanced/using-the-platform/settings/settings-users.md) — placing users in groups


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spectralink.net/amie-advanced/using-the-platform/settings/settings-groups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.