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

# Delete a hierarchy

Remove a hierarchy node after you confirm the impact on the tree.

Use **Remove Node** to delete a hierarchy node.

### Before you start

Confirm that:

* the selected node is the one you intend to remove
* the node is no longer needed
* you reviewed the impact on child nodes, devices, and user assignments

Use this action only when the node should be removed from the tree.

{% hint style="warning" %}
Review the selected branch carefully before you delete it. Deleting the wrong node can affect access, placement, and later hierarchy work.
{% endhint %}

### Delete 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 remove.
{% endstep %}

{% step %}

### 3. Open the delete action

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

{% step %}

### 4. Review and confirm

Confirm the deletion only after you verify the selected node and its impact.
{% 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%2FtNmNqvXu7PNd0c7YfRNW%2FPicture196.png?alt=media&amp;token=5b1e90b8-e410-4689-9485-a8ecf6eb7204" 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%2F2pWzAcojtdapXwamOhwG%2FPicture197.png?alt=media&amp;token=7aa583e0-c41f-42ae-8942-b3e872b9d873" alt=""><figcaption></figcaption></figure></div>

### What to confirm before deletion

Review these checks before you continue:

* the node should not stay in the structure
* the selected branch is correct
* any follow-up work on users, devices, or replacement nodes is planned

Stop if you cannot confirm the branch impact. Use [Edit a hierarchy](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/edit-a-hierarchy) when the node should remain but needs different details.

### Verify the result

After you confirm the action, check that:

* the node no longer appears in the tree
* adjacent branches still reflect the intended structure
* users know if follow-up hierarchy work is required

### Troubleshooting checks

If you are unsure whether to delete the node, stop and review:

* whether the change should be an edit instead
* whether the node should move under another branch through a different workflow
* whether the node is still needed for device ownership or access

### Result

The selected hierarchy is removed from the tree after its impact on access, placement, and replacement structure is confirmed.

### Next steps

* [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) — replace the node with a new top-level branch if needed
* [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) — rebuild the structure under a different parent if 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/delete-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.