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

# Add a child hierarchy

Add a new hierarchy node under an existing parent.

Use **Extend Node** to add a child hierarchy under an existing node.

### Before you start

Prepare:

* the correct parent node
* the new hierarchy **Name**
* the new hierarchy **Entity Type**

Confirm that the new node belongs under the selected parent and not at the root level.

Use a child node when it inherits the selected branch's operational scope. Use a root node when it needs an independent top-level branch.

### Add a child hierarchy

{% stepper %}
{% step %}

### 1. Open Hierarchies

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

{% step %}

### 2. Select the parent node

Choose the node that should own the new child hierarchy.
{% endstep %}

{% step %}

### 3. Open the child node action

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

{% step %}

### 4. Enter the new hierarchy details

Enter the required values for the child node, then review the parent before you save.
{% endstep %}

{% step %}

### 5. Save the node

Save the new hierarchy.
{% 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%2FPz39hf3pgT3gh9Wjb6B3%2FPicture188.png?alt=media&amp;token=9e23fece-b262-4e83-a6de-722f9a65268b" 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%2FrBgMLoozIRhxUMlAvv9B%2FPicture189.png?alt=media&amp;token=01cc07fe-9d77-4467-944d-2f21826c9899" 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%2FIRHa42WV9r9dXnAp2ZIu%2FPicture190.png?alt=media&amp;token=b20639f3-842f-44ef-9b70-96e9237dd13c" alt=""><figcaption></figcaption></figure></div>

### Required values

New child hierarchies require at least:

* **Name**
* **Entity Type**

Use values that clearly identify the node in the tree.

### Verify the result

After you save, confirm that:

* the new node appears under the intended parent
* the node name is correct in the tree
* the node is available for later user or device assignment

Do not assign users or move devices until the node appears in the expected branch.

### Common checks

If the result is not correct, check these first:

* the wrong parent was selected before you opened **Extend Node**
* the new node should have been created as a root hierarchy instead
* a required field was left blank

### Result

The new hierarchy is added under the selected parent node and is ready for later assignment work.

### Next steps

* [Edit a hierarchy](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/edit-a-hierarchy) — refine the new node details
* [Hierarchy - user management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/hierarchy-user-management) — manage access at the new node


---

# 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/add-a-child-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.