> 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-root-hierarchy.md).

# Add a root hierarchy

Add a new hierarchy at the top level of the organization tree.

Use **Root Node** to add a hierarchy directly under the root level.

### Before you start

Prepare:

* the new hierarchy **Name**
* the new hierarchy **Entity Type**
* confirmation that the node belongs at the top level

Use this action only when the new hierarchy should not sit under an existing parent node.

Use a root node only for an independent top-level branch. Create a child node when the new hierarchy belongs within an existing branch.

### Add a root hierarchy

{% stepper %}
{% step %}

### 1. Open Hierarchies

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

{% step %}

### 2. Open the root node action

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

{% step %}

### 3. Enter the new hierarchy details

Enter the required values for the new top-level node.
{% endstep %}

{% step %}

### 4. Save the new node

Save the hierarchy and return to the 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%2Fl4fTw6D96lfX07FyU6bn%2FPicture191.png?alt=media&amp;token=8d9d0fcb-3e30-443f-a5f2-1e8d5476bc1d" 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%2FKH81ARz8eArWajqbVput%2FPicture192.png?alt=media&amp;token=c5909c2a-4a21-4bb6-a477-a5150d08556c" alt=""><figcaption></figcaption></figure></div>

### Required values

New root hierarchies require at least:

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

Use a name that clearly distinguishes the root node from existing branches.

### Verify the result

After you save, confirm that:

* the new node appears at the root level
* the name and entity type are correct
* the new hierarchy is ready for child nodes, users, or device placement

Do not create child nodes or assign devices until the top-level placement is correct.

### Common checks

If the node appears in the wrong place, check these first:

* the new hierarchy should have been added as a child node instead
* the entered values do not clearly identify the new top-level branch
* the action was opened from the wrong path

### Result

The new hierarchy is added at the root level and is ready for child nodes or assignment work.

### Next steps

* [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) — build the next level under the new root
* [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 node details 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/add-a-root-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.