> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/help-center/account-management/organization-management/changing-organization-ownership.md).

# Changing organization ownership

#### I want to access my organization with a different email address <a href="#i-want-to-access-my-organization-with-my-different-email-address" id="i-want-to-access-my-organization-with-my-different-email-address"></a>

If you would like to change the email that your FieldDoc account is registered to, please email <support@fielddoc.com>.

#### I want to transfer my organization to a different user <a href="#i-want-to-transfer-my-organization-to-a-different-user" id="i-want-to-transfer-my-organization-to-a-different-user"></a>

Multiple users can belong to the same organization in FieldDoc. Navigate to Organization > Members to add or revoke membership access. You can also change the permission level from admin to read-only, when necessary. Generally, all admins have the same rights and can manage users and data management. So if you change another user's permission from read only to admin, they will be able to revoke your access. &#x20;

If you would like to leave the organization to fully remove your rights as owner, ask the other admin to remove you from the organization. This means you will loose the access to content.


---

# 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://help.fielddoc.org/help-center/account-management/organization-management/changing-organization-ownership.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.