> 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-device-management/verifone-central/tenants.md).

# Tenants

Use **Tenants** to separate devices, users, and visibility by customer or operational boundary.

Tenant access helps control who can view, manage, and support each part of the estate.

### Before you start

Confirm that:

* your role allows you to view or manage tenants
* you are working in the correct estate or customer context
* you know whether you need to add, review, edit, or delete a tenant

Prepare these details when available:

* tenant name
* customer or reseller context
* any devices or users that must belong to the tenant

{% hint style="info" %}
Tenant operations can depend on your assigned access scope and licensed features. Tenant management is available in both the UI and API.
{% endhint %}

### What tenants control

Use tenants to:

* separate device portfolios by merchant, reseller, or business unit
* limit visibility so users see only the devices and operations they are allowed to access
* support tenant-specific device management and diagnostic workflows

### Who can manage tenants

These are the main tenant access levels:

* **Estate Owner Admin** and **Verifone Admin** — add, edit, delete, and view tenants
* **Verifone Helpdesk** — view and edit tenants
* **Merchant Admin** and **Merchant User** — view tenants only

{% hint style="info" %}
Actual visibility can also depend on the tenant, hierarchy, or group assigned to the user. For broader access details, see [User roles and permissions](/verifone-central-device-management/verifone-central/user-roles-and-permissions.md).
{% endhint %}

### Open tenants

Go to **Verifone Central** → **Device Management** → **Tenants**.

### Common tenant tasks

Tenant work usually follows this flow:

1. Create a tenant.
2. Review the tenant details.
3. Update the tenant when ownership or setup changes.
4. Delete the tenant when it is no longer needed.

Use:

* [Add a tenant](/verifone-central-device-management/verifone-central/tenants/add-a-tenant.md)
* [View a tenant](/verifone-central-device-management/verifone-central/tenants/view-a-tenant.md)
* [Edit a tenant](/verifone-central-device-management/verifone-central/tenants/edit-a-tenant.md)
* [Delete a tenant](/verifone-central-device-management/verifone-central/tenants/delete-a-tenant.md)

### How tenants affect device management

When tenant access is configured correctly, users can:

* work only with the devices available to their tenant scope
* switch context when they are allowed to support multiple customers
* move or remove devices across tenant boundaries when their role and license permit it

### Result

Tenants help you organize the estate, control visibility, and route device management work to the right users.

### Next steps

* [Add a tenant](/verifone-central-device-management/verifone-central/tenants/add-a-tenant.md)
* [Edit a tenant](/verifone-central-device-management/verifone-central/tenants/edit-a-tenant.md)
* [Delete a tenant](/verifone-central-device-management/verifone-central/tenants/delete-a-tenant.md)
* [User roles and permissions](/verifone-central-device-management/verifone-central/user-roles-and-permissions.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/verifone-central-device-management/verifone-central/tenants.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.