> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/account-management/account-settings.md).

# Account Settings

Manage your Mindee account.

A Mindee account is required for logging into the platform.

However, models and API keys are stored at the organization level.

When you create your Mindee account, a default organization will be created. Your account will be the [owner](/account-management/organizations.md#member-roles) of this organization.

You can be a member of multiple organizations.

## Access Account Settings

Click on "<i class="fa-gear">:gear:</i> Settings" in the main menu, then on the "Account" tab.

Or simply click here: <a href="https://app.mindee.com/settings?tab=account" class="button primary">Go to Account page</a>

## Personal Information

### Email

If you connect to Mindee using your email and a password, you can change your email address. You'll be sent a link to confirm the new email address.

If you connect to Mindee through a 3rd party, such as Google or Github, the email address used will be displayed. It is not possible to change it, you'll need to connect with another provider or use an email/password login.

### Full Name

You can change your full name as it appears in the Mindee platform to other users in your organization.

## Danger Zone

### Delete Account

You can delete your account and all its associated data.

{% hint style="danger" %}
Deleting your account is an **irreversible action**, all data will be lost forever!
{% endhint %}

Deleting your account will also delete all organizations in which you are the only owner.

Any non-owner users will lose access to these organizations.


---

# 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.mindee.com/account-management/account-settings.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.