> 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/hierarchy-user-management.md).
# Hierarchy - user management
Review, reuse, and remove user assignments for a selected hierarchy node.
Use hierarchy user management to view, assign, and unassign users for a selected node.
### When to use this page
Use this page when access should follow a specific hierarchy node.
Use it to review current assignments, reuse users from another node, or remove users from the selected node.
### Before you start
Confirm that:
* you know which hierarchy node needs the access change
* you know whether you need to add or unassign users
* you have permission to manage user assignments for the node
Identify the user, target node, and intended access outcome before changing assignments. User assignments affect access at the selected hierarchy scope.
Review the current list before copying or unassigning users. This prevents removing access that another workflow still requires.
### Open hierarchy user management
{% stepper %}
{% step %}
### 1. Open Hierarchies
Go to **Verifone Central** → **Device Management** → **Hierarchy/Group Management** → **Hierarchies**.
{% endstep %}
{% step %} 
{% endstep %}
{% step %}
### 2. Open the Users action
Select **Actions** → **Update Hierarchy** → **Edit Node** → **Users**.
{% endstep %}
{% step %} 
{% endstep %}
{% step %} 
{% endstep %}
{% step %}
### 3. Select the target node
Select the node checkbox, then select **Continue**.
{% endstep %}
{% endstepper %}
The page shows the users currently assigned to the selected node.
### Add users from another node
Select **Add users from other node**.
Use this option when the selected node should inherit or reuse existing assignments from another node.
After you start the action, follow the prompts to choose the source node and users to reuse.
Compare the source and target node before confirming. Copy only users who need access at the target scope.
### Unassign users
{% stepper %}
{% step %}
### 1. Select the users
Select one or more users from the current node assignment list.
{% endstep %}
{% step %}
### 2. Remove the assignments
Select **Unassign Users**.
{% endstep %}
{% endstepper %}
Confirm each selected user can lose access to the node. Unassigning a user changes their access at that node. It does not change the hierarchy structure.
{% hint style="info" %}
The page shows the selected node name and total user count. Use **Results per page** to change the visible list size.
{% endhint %}
### Verify the result
After you update assignments, confirm that:
* the selected node name is still correct
* the user list reflects the intended change
* the total user count matches the updated assignments
* each added or removed user has the intended access outcome
### Common checks
If the result does not match expectations, check these first:
* the wrong node was selected before you opened **Users**
* the user should have been copied from another node instead of removed
* the current page is showing only part of the list because of pagination
* the assignment was changed on a different node than intended
### Result
You can review node-level access and keep user assignments up to date.
### Next steps
* [Hierarchies](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/hierarchies) — return to the hierarchy tree
* [Edit a hierarchy](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/manage-hierarchies-and-groups/edit-a-hierarchy) — update node details if the structure also needs a change
---
# 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/hierarchy-user-management.md?ask=&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.
