> 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-getting-started/verifone-central/verifone-central-device-manager/devices/manage-hierarchies-and-groups/manage-groups.md).
# Manage groups
Create, update, and remove flexible device groups for operational work.
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
Define the group’s purpose, expected members, and owner. Use a distinct name that communicates its operational use.
Review existing groups first. Reuse a suitable group when it already serves the same purpose.
### 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 %}
### 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**.
After creation, confirm the group name and membership scope before using it for an operational task.
#### 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**.
Review the effect on scheduled work before changing a group used by another team.
#### Delete a group
Use **Delete Group** only when the collection is no longer needed.
Select **Actions** → **Delete Group**.
Before deletion, confirm that no active workflow relies on the group. If the group may be needed later, update its details instead.
### 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
* group membership supports the intended task without changing device hierarchy
### 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](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups) if you need to recheck the difference
### Result
You can manage device groups from one page.
### Next steps
* [View devices](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/view-devices) — work with device lists that feed group actions
* [Manage hierarchies and groups](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups) — 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/devices/manage-hierarchies-and-groups/manage-groups.md?ask=&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.
