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

# Add a tenant

Create a new tenant record and verify it appears in the correct customer context.

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

Search the tenant list for the intended name before creating a record. Stop if the tenant already exists or a similarly named record needs review.

### 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="https://1786380399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdzivQyj8aHN5Kvmx8apX%2Fuploads%2FnfSkt7icIVnmPcY01PZ0%2FPicture223png.png?alt=media&amp;token=49dff9fc-a1a4-48d1-9130-ddb969337855" 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%2FdjWdnNV36HHRM9JXlH1h%2FPicture218.png?alt=media&amp;token=3768e974-c1a3-4eeb-a390-9d651ba2a932" 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%2F55JuikzzMFdpwS0vNtz1%2FPicture219.png?alt=media&amp;token=20221fc2-6356-4003-9cad-6981a854846b" 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%2FHle8YyQIjj1ovsIUQwhC%2FPicture220.png?alt=media&amp;token=bddb9339-0e1a-4d63-9ac6-e0634e1abe92" 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%2FQeVp7voL55PsT5WLSXmA%2FPicture221.png?alt=media&amp;token=e840179a-e7ad-4c6c-ad12-3967cb1bc09b" 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%2Fz6vOnTfSB3GPQEXFDCfx%2FPicture222.png?alt=media&amp;token=3b61b825-1689-4837-8c47-278a579ede1f" 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

Record the tenant name and customer or reseller context in the setup handoff. This lets the next operator verify the correct record before adding devices or users.

### 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
* a similar tenant already exists — stop and resolve the duplicate before further setup

### Result

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

### Next steps

* [View a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/view-a-tenant) — review the new tenant record
* [Edit a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/edit-a-tenant) — update the tenant if setup needs changes
* [Delete a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/delete-a-tenant) — remove the tenant if it was created in error
* [Tenants](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants) — 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 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/tenants/add-a-tenant.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.