> 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/carto-support-access.md).

# CARTO Support Access

Admins can authorize the CARTO Support team to access their organization to help troubleshoot issues or facilitate onboarding. This access is most commonly used when the CARTO Support team struggles to replicate a technical issue or when a complex problem has been escalated and needs further investigation.

## How to enable Support Access

1. As an Admin, go to the Settings.
2. Locate the *Enabling Support access* section in the *General* settings. Click on *Enable access.*
3. Select a duration for the support account and tick the box to confirm that you want to authorize access.
4. Click on the *Enable access* button.

{% hint style="info" %}
All support users have an expiration date. Admins can set their duration when they first enable access, choosing between 1 day, 7 days, 30 days, 90 days, or 180 days.
{% endhint %}

Enabling CARTO Support Access will create a new [Admin-level user](/carto-user-manual/settings/users-and-groups/managing-user-roles.md#available-roles) in your organization, which authorized members of our support team will use to access your organization.

Once enabled, all Admins within the organization will have full visibility on who enabled Support Access and when, as well as the date when it is due to expire.

Once the expiration date has passed, the support user will be permanently deleted, and CARTO will no longer have access to your organization. If the support user created any Maps or Workflows, these will be transferred to the Admin user who enabled Support Access.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-021684d68200c44bf3d8ebdcaffd50599efd3b44%2FScreenshot%202024-07-23%20at%2010.09.33.png?alt=media" alt=""><figcaption><p>Enabling Support Access</p></figcaption></figure>

## Revoking Support access

Admins can revoke Support access at any time by clicking on the *Revoke access* button.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-c7a40353ae552c56876e17304a0a0f6a4f1a3fd0%2FScreenshot%202024-07-23%20at%2012.10.22.png?alt=media" alt=""><figcaption></figcaption></figure>

1. In the *Enabling Support access* section of the *General* settings, click on *Revoke access.*
2. A new modal will appear. Select a user that will inherit any asset created by the support account.
3. Click on Revoke access.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-bebc83810c7b96efb150969afc0cc91756153b3c%2FScreenshot%202024-07-23%20at%2010.12.42.png?alt=media" alt=""><figcaption></figcaption></figure>

Once this is done, the support user will be permanently deleted and CARTO will no longer have access to your organization. Any assets created by the support user will be transfered to the selected user.


---

# 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/carto-support-access.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.
