> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/es/knowledge-base/knowledge-base-articles/consequences-of-deleting-a-devolutions-account-on-devolutions-cloud.md).

# Consecuencias de eliminar una Devolutions Account en Devolutions Cloud

Comprenda qué ocurre cuando se elimina una Devolutions Account, incluida la pérdida de acceso para los usuarios de Devolutions Cloud y las transferencias de propiedad necesarias.

La eliminación de las Devolutions Accounts se puede realizar rápidamente desde la página de perfil del Devolutions Portal.

{% hint style="danger" %}
¡ESTO NO SE PUEDE DESHACER!

Una vez que haya eliminado una cuenta, no podrá revertir esa acción.
{% endhint %}

<table><thead><tr><th width="230.5999755859375">Para los usuarios de Devolutions Cloud</th><th width="279.5999755859375">Para los propietarios de Devolutions Cloud</th></tr></thead><tbody><tr><td>El Devolutions Cloud no se elimina, pero los usuarios ya no tienen acceso a él.</td><td>El propietario deberá transferir la propiedad a otro usuario y esperar a que se elimine el Devolutions Cloud antes de poder eliminar la Devolutions Account.</td></tr></tbody></table>


---

# 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.devolutions.net/cloud/es/knowledge-base/knowledge-base-articles/consequences-of-deleting-a-devolutions-account-on-devolutions-cloud.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.