> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/kore/iam/how-to/transfer-account-ownership.md).
# Transfer Account Ownership
There is only ever one account owner who has unlimited access to the account, such as updating billing details.
The account owner may wish to transfer ownership to another user later through the [KORE Console User Management](https://console.korewireless.com/users).
## Scenario 1: The current account owner still has access
If the current account owner still has access to their user account, they can transfer ownership to any other `admin` user within the account.
If the user you want to transfer ownership to doesn't already exist in your account, you can [invite ](/kore/iam/users.md#user-invites)them as an `admin` . Once accepted, you can then transfer ownership.
{% hint style="info" %}
The role of the current account owner will be demoted to an admin.
{% endhint %}
## Scenario 2: The current account owner does not have access
There may be times when the existing owner has left the organization or cannot log in. You must contact support to transfer ownership to another user in these instances.
---
# 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.korewireless.com/kore/iam/how-to/transfer-account-ownership.md?ask=&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.
