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

# Add a tenant

Create a new tenant record in Device Management.

### Before you start

Confirm that:

* your role allows you to add tenants
* you are working in the correct estate or customer context
* you have the tenant details ready for setup

Prepare these details when available:

* tenant name
* customer or reseller context
* any setup values tied to devices or users that will belong to the tenant

### Add a tenant

{% stepper %}
{% step %}

### 1. Open the add flow

Go to **Verifone Central** → **Device Management** → **Tenants** → **Add Tenant**.
{% endstep %}

{% step %}

### 2. Enter the tenant details

Complete the tenant fields for the new record.
{% endstep %}

{% step %}

### 3. Review the configuration

Confirm that the tenant belongs to the correct customer or reseller scope.
{% endstep %}

{% step %}

### 4. Save the tenant

Save the new tenant record.
{% endstep %}
{% endstepper %}

<div data-with-frame="true"><figure><img src="/files/6vq9G2MlFSzlnXtTNbQg" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/qa76q9Z45akEnxKCnrh6" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/1cJEA0D6B6kd10JdYDNh" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/lrzWQfrX0VpIFWky1HoY" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/wQ7qfhqDhI7CtHxkjJhL" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/AGKA80CJvD45DMjZA1Cz" alt=""><figcaption></figcaption></figure></div>

### What to check before saving

Confirm that:

* the tenant name is correct
* the tenant belongs to the expected customer or reseller context
* the configuration matches the users or devices you plan to manage under this tenant

### Verify the result

After you save the tenant, confirm that:

* the new tenant appears in the tenant list
* the tenant name is correct
* the tenant opens in the expected customer context
* the record is ready for later review or editing

### Common follow-up checks

Use these checks if the result is not what you expected:

* the tenant does not appear — confirm you saved the record in the correct customer context
* the details look wrong — open the tenant and review the saved values
* you need to continue setup — open the tenant and make the required edits

### Result

The tenant is added and becomes available in the tenant list.

### Next steps

* [View a tenant](/verifone-central-device-management/verifone-central/tenants/view-a-tenant.md) — review the new tenant record
* [Edit a tenant](/verifone-central-device-management/verifone-central/tenants/edit-a-tenant.md) — update the tenant if setup needs changes
* [Delete a tenant](/verifone-central-device-management/verifone-central/tenants/delete-a-tenant.md) — remove the tenant if it was created in error
* [Tenants](/verifone-central-device-management/verifone-central/tenants.md) — return to the tenant workflow


---

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