> 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/connections/deleting-a-connection.md).
# Deleting connections
You can view and manage all your existing connections in the *Connections* section of the Workspace. To manage a connection, click the three-dot menu on the connection card. This opens a menu with three options: Edit, Share, and Delete.
When you click *Delete*, a confirmation dialog appears. If the connection is being used by maps, workflows, tokens, etc., you can choose from two options:
* **Update to use another connection:** Automatically updates all dependent maps, workflows, tokens, etc. to use a different connection. The new connection must be of the same provider (i.e. Snowflake, Databricks, etc.).
* **Delete along with the connection:** Permanently removes the connection and all maps, workflows, tokens, etc. that use it. This action cannot be undone.
{% hint style="info" %}
**Note:** You cannot delete shared connections. To delete a shared connection, first make it private to remove access for other users.
{% 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/connections/deleting-a-connection.md?ask=&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.
