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

# Delete a tenant

Remove a tenant after you confirm the tenant is no longer needed.

Remove a tenant record.

### Before you start

Confirm that:

* your role allows you to delete tenants
* you selected the correct tenant
* the tenant is no longer needed
* you understand the impact of removing the tenant from ongoing management

Before deleting, identify any devices, users, or workflows that still rely on the tenant. Stop if an active operational process needs the record.

### Delete a tenant

{% stepper %}
{% step %}

### 1. Open the tenant list

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

{% step %}

### 2. Select the tenant

Open or highlight the tenant you want to remove.
{% endstep %}

{% step %}

### 3. Choose the delete action

Select the delete action for the tenant.
{% endstep %}
{% endstepper %}

Click the delete icon for the selected tenant.

<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%2F0AZE3KTazSCKQyUPQK3I%2FPicture228.png?alt=media&amp;token=fbd38f0e-a9c3-4f30-acd3-5e4dea43cbb3" 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%2Fx8uGKH4zcUUb7MFHgRtL%2FPicture229.png?alt=media&amp;token=d469fa72-87c5-4be5-b1e7-5e02db7e3f97" alt=""><figcaption></figcaption></figure></div>

Confirm the action by selecting **Yes**.

{% hint style="warning" %}
Delete a tenant only after you confirm it is the correct record and no longer needed for ongoing management.
{% endhint %}

### What to review before you confirm

Check these points before deletion:

* the tenant name matches the record you intend to remove
* the tenant is not needed for active operational work
* you do not need to keep the tenant for later review or editing

Capture the tenant name and customer or reseller context before confirming. This creates a clear deletion record for follow-up review.

### Verify the result

After you confirm deletion, check that:

* the tenant no longer appears in the tenant list
* the deleted record is no longer available for editing
* no further tenant cleanup is required
* remaining tenants still match the expected customer or reseller scope

### Common follow-up checks

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

* the tenant is still visible — refresh the list and confirm the action completed
* you are unsure whether the right tenant was removed — compare the remaining tenant list with the expected records
* the tenant should not have been deleted — review your tenant governance process before further cleanup
* an active workflow needs the tenant — stop related changes and escalate through your tenant governance process

### Result

The selected tenant is deleted.

### Next steps

* [View a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/view-a-tenant) — review the remaining tenant list
* [Add a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/add-a-tenant) — create a replacement tenant if needed
* [Edit a tenant](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/tenants/edit-a-tenant) — update another tenant record
* [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/delete-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.