> 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/edit-a-hierarchy.md).

# Edit a hierarchy

Update the details of an existing hierarchy node.

Use **Edit Node** to update hierarchy details.

### Before you start

Confirm that:

* you selected the correct node in the tree
* you know which details need to change
* the update does not belong on a different node

Review the current values before you edit them.

### Edit a hierarchy

{% stepper %}
{% step %}

### 1. Open Hierarchies

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

{% step %}

### 2. Select the node

Choose the hierarchy node you want to update.
{% endstep %}

{% step %}

### 3. Open the edit form

Select **Actions** → **Update Hierarchy** → **Edit Node** → **Details**.
{% endstep %}

{% step %}

### 4. Update the hierarchy details

Change the required values, then review the update before you save.
{% endstep %}

{% step %}

### 5. Save the changes

Save the node and return to the hierarchy tree.
{% 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%2Fto6TlPEWXc9STiCMOjQF%2FPicture193.png?alt=media&amp;token=5760b999-a4af-4eca-9a90-9bfce8104595" alt=""><figcaption></figcaption></figure></div>

<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%2FcY3q42oufrLy99ZVv6XQ%2FPicture194.png?alt=media&amp;token=4b157c98-6132-4ba2-a867-bcea2e7951e6" alt=""><figcaption></figcaption></figure></div>

<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%2F2wfe82AEmCgGo4s9k4N5%2FPicture195.png?alt=media&amp;token=6e3828c8-ec12-40ca-aefa-918d1eeb5a90" alt=""><figcaption></figcaption></figure></div>

### Review before you save

Check these points before you confirm the edit:

* the selected node is still the intended one
* the updated values match the business structure you want
* the change does not require a new node instead of an edit

Record the current values and intended values before saving. This makes it easier to verify the change and explain it to affected users.

### Verify the result

After you save, confirm that:

* the tree shows the updated details
* the node still sits in the correct branch
* related users or device placement can still be managed as expected

### Troubleshooting checks

If the update does not look right, check these first:

* the wrong node was selected before you opened **Edit Node**
* the intended change should have been a child or root node addition
* the edited values are too similar to another node and cause confusion

### Result

The selected hierarchy is updated with the new details. The node remains in its existing branch unless a separate structure action changes it.

### Next steps

* [Hierarchy - user management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/hierarchy-user-management) — review access at the updated 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 node if it is no longer needed


---

# 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/edit-a-hierarchy.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.