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

# View a tenant

Review tenant records and open the right tenant for follow-up actions.

Review tenant records in your estate.

### Before you start

Confirm that:

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

Identify the tenant name and expected customer or reseller context before opening the record.

### View a tenant

{% stepper %}
{% step %}

### 1. Open the tenant list

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

{% step %}

### 2. Review the tenant list

Scan the available tenant records and confirm you are in the correct scope.
{% endstep %}

{% step %}

### 3. Open the tenant

Select the tenant you want to review.
{% 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%2FDeBDpG8eJdDXtCpco6QS%2FPicture230.png?alt=media&amp;token=31217b8a-cb64-4927-b1cc-59cc59a16dcc" alt=""><figcaption></figcaption></figure></div>

### What to review

Use the tenant view to confirm:

* tenant name and basic details
* available tenant records in the estate
* which tenant you want to edit or delete

Before a follow-up action, confirm the tenant identity and scope again. Do not edit or delete a tenant selected only by a similar name.

### Choose the next action

After you open the tenant:

* use [Edit a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/edit-a-tenant) when tenant details need to change
* use [Delete a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/delete-a-tenant) when the tenant should be removed
* use [Add a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/add-a-tenant) when another tenant must be created

### Verify the result

After you review the tenant, confirm that:

* you opened the correct tenant record
* the tenant details support the next action you need to take
* the tenant is in the expected estate or customer scope
* the next action has the correct operational owner and purpose

### Result

The selected tenant details are displayed. You can then decide whether to update the tenant or remove it.

### Next steps

* [Add a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/add-a-tenant) — create another tenant
* [Edit a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/edit-a-tenant) — update the selected tenant
* [Delete a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/delete-a-tenant) — remove the selected tenant
* [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/view-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.