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

# Personal settings

Manage your CARTO account and check your own consumption

Every user in the organization, except [Guest viewers](/carto-user-manual/settings/users-and-groups/managing-user-roles.md#guest-viewers), can open the **Settings** to manage their own account and check their consumption from the **Personal** section.

## Profile

**Settings > Profile** shows your email, your role in the organization, and how you sign in to CARTO.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-d7ac80cca1ee9c45bd6070027cf0826fae76331c%2Fuser-settings-profile.png?alt=media" alt=""><figcaption></figcaption></figure>

From here you can:

* **Change password:** set a new password for signing in to CARTO. This is only available if you sign in with email and password; if your organization uses [SSO](/carto-user-manual/settings/sso.md), your password is managed by your Identity Provider.
* **Delete my user:** permanently delete your CARTO user. This removes your profile and revokes your access to the organization.

{% hint style="danger" %}
Deleting your user cannot be undone. The assets you own, such as maps, workflows, and connections, are transferred to your organization's [default Admin](/carto-user-manual/settings.md#general).
{% endhint %}

## Usage

**Settings > Usage** shows how much you have personally consumed of each quota: [Usage quota](/carto-user-manual/settings/quotas-and-rate-limits/understanding-your-organization-quotas.md#usage-quota), [LDS quota](/carto-user-manual/settings/quotas-and-rate-limits/understanding-your-organization-quotas.md#location-data-services-lds), and [AI quota](/carto-user-manual/settings/quotas-and-rate-limits/understanding-your-organization-quotas.md#carto-managed-ai). These are your own individual figures, not your organization's totals.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-9835d39f48187c44a2a16804954a3d9cb5b22ea5%2Fuser-settings-usage.png?alt=media" alt=""><figcaption></figcaption></figure>

If an Admin has set a [quota limit](/carto-user-manual/settings/quotas-and-rate-limits/managing-quotas.md) for you, or for a group you belong to, the page also shows that limit and how much of it you have consumed. Once you reach a limit you are blocked from consuming more of that quota, so contact your Admin if you need more.


---

# 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.carto.com/carto-user-manual/settings/personal-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.