> 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.md).

# Settings

The **Settings** is where you manage your CARTO account and, if you are an Admin, configure your organization. It is organized in three sections:

* **Personal:** your [profile and your own consumption](/carto-user-manual/settings/personal-settings.md). Available to every user except [Guest viewers](/carto-user-manual/settings/users-and-groups/managing-user-roles.md#guest-viewers).
* **CARTO AI:** [CARTO AI configuration](/carto-user-manual/settings/carto-ai.md), the [CARTO MCP Server](/carto-for-agents/mcp-server.md), and [CARTO AI Analytics](/carto-user-manual/settings/carto-ai/carto-ai-analytics.md).
* **Organization:** your organization's details, plan and quota, [users and groups](/carto-user-manual/settings/users-and-groups.md), [activity data](/carto-user-manual/settings/activity-data.md), governance policies, integrations, and more.

Admins have access to all sections. Other users see the Personal section plus a reduced set of the CARTO AI and Organization sections, where organization pages are read-only.

## General

The first section of the Organization settings is **General**, which provides core organization information and settings.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-8361d772ca100c9a5b1c547a72afd555d9ae7d52%2FScreenshot%202025-02-24%20at%2012.51.18.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-02a8391c322f4508854a97d2762292f1f63b61da%2Fsettings-default-admin.png?alt=media" alt=""><figcaption><p>The default admin selector in Settings > General</p></figcaption></figure>

The available settings in the General section are:

* **Default admin:** Choose the Admin who inherits the assets (maps, workflows, connections, and so on) of users who are removed from the organization or downgraded, including users who [delete their own user](/carto-user-manual/settings/personal-settings.md#profile).
* [**Enabling Support Access**](/carto-user-manual/settings/carto-support-access.md)**:** Invite the CARTO Support team to your organization. This is commonly used for troubleshooting and onboarding.
* **Delete organization:** Delete your organization and all its related assets. This action cannot be undone.

{% hint style="danger" %}
Please remember that deleting your organization is definitive and there's no possibility of recovering your information such as maps or connections, so proceed with caution.
{% endhint %}


---

# 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.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.