> For the complete documentation index, see [llms.txt](https://docs.arnica.io/arnica-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arnica.io/arnica-documentation/platform-operations/tenant-management/changing-the-tenant-owner.md).

# Changing the Tenant Owner

How to request a transfer of the Arnica tenant Owner role.

Every Arnica tenant has a single Owner, only the Owner can rename or delete the tenant, and that role cannot be changed from the Users & Roles page. To transfer ownership, submit a request to Arnica support.

## Before you request a transfer

1. **Choose the new Owner.** Pick a full-time employee who is responsible for application security or platform tooling. Use their individual corporate email address. Do not use shared mailboxes, distribution lists, or contractor accounts.
2. **Make the new Owner an Admin.** Only an existing Admin in your tenant can become the Owner. If the person is not a member yet, invite them from **Admin → Security → Users & Roles** and confirm they have accepted the invite (their **Status** column shows **accepted**). Then set their role to **Admin**.
3. **Confirm a backup Admin.** Make sure at least one other person besides the current and new Owner has the Admin role, so the tenant is never left with a single privileged user.

{% hint style="info" %}
If the new Owner is not an Admin in your tenant when you send the request, Arnica cannot complete the transfer. When RBAC is SSO-managed, the Admin role comes from your identity provider group mapping rather than the Users & Roles role picker. See [Role Based Access Control (RBAC)](/arnica-documentation/security/role-based-access-control-rbac.md).
{% endhint %}

4. **Save any API token secret that only the leaving person has.** Changing the Owner does not change API tokens, integrations, scheduled reports, or notification routing. An API token secret is shown only when the token is created and cannot be viewed again. If that person is the only one who saved it, store the secret or create a new token before they leave. The existing token keeps working after the Owner changes.

## Request the transfer

Create a ticket through the [Support portal](/arnica-documentation/platform-operations/support-portal.md), or send an email to <support@arnica.io>.

### Who can send the request

* The current Owner, from the email address they use to sign in to Arnica.
* If the current Owner is unavailable (for example, they have left your company), an Admin in your tenant can send the request instead. A security or IT leader at your company (for example, your CISO, VP of Engineering, or IT director) must approve it in writing on the same email thread.

### Email domain requirements

* The sender, the new Owner, and any approver must all use email addresses on a domain associated with your tenant (for example, `@yourcompany.com`).
* Requests from personal email providers (such as Gmail or Outlook.com) or from unrelated domains are rejected.
* If your company uses more than one domain (for example, after an acquisition), ask your Arnica account contact to add the extra domains to your tenant before you send the request.

### What to include

* Tenant name
* Current Owner email
* New Owner email (must already be an Admin in the tenant)
* Name and title of the person sending the request
* Reason for the change
* Preferred date for the change

CC the new Owner, and the current Owner if they are still with your company.

## How Arnica verifies the request

Before making any change, Arnica support:

1. Checks that the sender, new Owner, and any approver use your tenant's domain, and that the new Owner is an Admin.
2. Confirms the request with your company's account contact on record, using contact details Arnica already has rather than details in the request email.

Once the request is verified, Arnica makes the change. Support confirms by email when the transfer is complete and notifies the former Owner if they are still reachable.