> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-device-management/verifone-central/devices/manage-hierarchies-and-groups/manage-groups.md).

# Manage groups

Use **Manage groups** to create, update, and remove device groups.

Groups help you organize devices outside the hierarchy tree.

### When to use groups

Use groups when devices should stay in their current hierarchy placement but still need to be collected for work.

Common uses include:

* bulk operational tasks
* cross-hierarchy reporting sets
* short-term working collections

### Before you start

Confirm that:

* a group is the right choice instead of a hierarchy move
* you know the operational purpose of the group
* you know whether you need to create, edit, or delete a group

### Open groups

{% stepper %}
{% step %}

### 1. Open Groups

Go to **Verifone Central** → **Device Management** → **Hierarchy/Group Management** → **Groups**.
{% endstep %}

{% step %}

### 2. Review the list

Check the current groups before you create or change one.
{% endstep %}
{% endstepper %}

<div data-with-frame="true"><figure><img src="/files/ZsJ67ReHcRZcMLM6luY6" alt=""><figcaption></figcaption></figure></div>

### Use the Actions menu

Open **Actions** to manage the selected group.

#### Create a group

Use **Create Group** when you need a new device collection for a specific workflow.

Select **Actions** → **Create Group**.

<div data-with-frame="true"><figure><img src="/files/6aqInDWG2vsEcWK5EvjP" alt=""><figcaption></figcaption></figure></div>

#### Edit group details

Use **Edit Group Details** when the current group setup still fits, but its details need to change.

Select **Actions** → **Edit Group Details**.

<div data-with-frame="true"><figure><img src="/files/YnuRGA6MFUdloXBGBjrV" alt=""><figcaption></figcaption></figure></div>

#### Delete a group

Use **Delete Group** only when the collection is no longer needed.

Select **Actions** → **Delete Group**.

<div data-with-frame="true"><figure><img src="/files/n9hJtVI1HUgHHeOcgM10" alt=""><figcaption></figcaption></figure></div>

### Verify the result

After you complete an action, confirm that:

* the group list shows the intended create, edit, or delete result
* the group still matches the operational purpose you planned
* you did not change a group that should remain available for another workflow

### Choose groups or hierarchies

Use these quick rules:

* use **Groups** when device placement should stay the same
* use **Hierarchies** when ownership or access should follow a business structure
* return to [Manage hierarchies and groups](/verifone-central-device-management/verifone-central/devices/manage-hierarchies-and-groups.md) if you need to recheck the difference

### Result

You can manage device groups from one page.

### Next steps

* [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) — work with device lists that feed group actions
* [Manage hierarchies and groups](/verifone-central-device-management/verifone-central/devices/manage-hierarchies-and-groups.md) — switch back to hierarchy planning


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/verifone-central-device-management/verifone-central/devices/manage-hierarchies-and-groups/manage-groups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.