> 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/configure-hierarchies.md).

# Configure hierarchies

Select a hierarchy node and move to the exact action you need.

Use **Configure hierarchies** to open the hierarchy tree and choose the right node action.

### When to use this page

Use this page when you already know the target node and need to decide what to do next.

Use it to move from the tree view to a specific task without guessing which action to open.

### Before you start

Confirm that you know:

* the node you want to manage
* whether the change is add, edit, or delete
* whether the change affects the current node or a new child node

### Open Hierarchies

{% stepper %}
{% step %}

### 1. Open the hierarchy tree

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

{% step %}

### 2. Select the node

Choose the node that matches the scope of your change.
{% endstep %}

{% step %}

### 3. Open the available actions

Select **Actions** and review the node operations.
{% endstep %}
{% endstepper %}

<div data-with-frame="true"><figure><img src="https://1786380399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdzivQyj8aHN5Kvmx8apX%2Fuploads%2FFARZyVCc4RBWvWBXftMz%2FPicture187.png?alt=media&amp;token=436113dc-5b15-43b8-b6da-a46f20b2481b" alt=""><figcaption></figcaption></figure></div>

### Choose an action

From the selected node, you can:

* [Add a child hierarchy](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/add-a-child-hierarchy) — create a node under the selected parent
* [Add a root hierarchy](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/add-a-root-hierarchy) — create a top-level node
* [Edit a hierarchy](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/edit-a-hierarchy) — update the selected node
* [Delete a hierarchy](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/delete-a-hierarchy) — remove the selected node

### Pick the right path

Use these rules before you continue:

* choose **Add a child hierarchy** when the selected node should stay and gain a child
* choose **Add a root hierarchy** when the new node should not sit under the selected parent
* choose **Edit** or **Delete** only after you confirm the selected node is correct

Choose the least disruptive action. Add a child when the existing branch remains valid. Edit only the selected node. Delete only when the node is no longer needed.

### Verify the selection

Before you open a task page, confirm:

* the selected node is highlighted in the tree
* the action matches the intended scope
* you are not changing the wrong branch of the hierarchy

### Result

You can move from the tree view to the exact hierarchy action with less risk of changing the wrong node. Recheck the tree after every completed action.


---

# 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/configure-hierarchies.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.