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

# Edit a tenant

Update an existing tenant record.

### Before you start

Confirm that:

* your role allows you to edit tenants
* you know which tenant needs to be updated
* you understand the impact of the change on tenant access or setup

Prepare these details when available:

* the tenant name or identifying details
* the values you need to change
* the expected customer or reseller context

### Edit a tenant

{% stepper %}
{% step %}

### 1. Open the tenant list

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

{% step %}

### 2. Select the tenant

Open the tenant you want to update.
{% endstep %}

{% step %}

### 3. Review the current details

Confirm that you selected the correct tenant and review the existing values.
{% endstep %}

{% step %}

### 4. Update the tenant information

Edit the tenant details that need to change.
{% endstep %}

{% step %}

### 5. Save the changes

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

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

Select the tenant to edit.

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

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

The tenant view can also display locked parameter templates and reference sets for the tenant.

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

### What to review while editing

Use the tenant view to confirm:

* the current tenant details
* related configuration tied to the tenant
* whether locked parameter templates or reference sets apply to this tenant

### Verify the result

After you save the changes, confirm that:

* the updated values appear on the tenant record
* the tenant is still in the correct customer or reseller scope
* any related configuration still matches the intended setup

### Common follow-up checks

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

* the wrong tenant was opened — return to the list and confirm the tenant identity before editing again
* the update does not look correct — compare the saved values with the intended configuration
* the tenant needs broader review — open the related tenant details and verify the full setup

### Result

The tenant details are updated and saved.

### Next steps

* [View a tenant](/verifone-central-device-management/verifone-central/tenants/view-a-tenant.md) — review the saved tenant details
* [Add a tenant](/verifone-central-device-management/verifone-central/tenants/add-a-tenant.md) — create another tenant if needed
* [Delete a tenant](/verifone-central-device-management/verifone-central/tenants/delete-a-tenant.md) — remove the tenant if it should no longer exist
* [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/edit-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.