> 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/fr/knowledge-base/knowledge-base-articles/consequences-of-deleting-a-devolutions-account-on-devolutions-cloud.md).

# Conséquences de la suppression d'un Devolutions Account sur Devolutions Cloud

Comprenez ce qui se passe lorsqu'un Devolutions Account est supprimé, y compris la perte d'accès pour les utilisateurs de Devolutions Cloud et les transferts de propriété requis.

La suppression des Devolutions Accounts peut se faire rapidement à partir de la page de profil du Devolutions Portal.

{% hint style="danger" %}
CETTE ACTION EST IRRÉVERSIBLE!

Une fois qu'un compte est supprimé, vous ne pourrez pas annuler cette action.
{% endhint %}

<table><thead><tr><th width="230.5999755859375">Pour les utilisateurs de Devolutions Cloud</th><th width="279.5999755859375">Pour les propriétaires de Devolutions Cloud</th></tr></thead><tbody><tr><td>Le Devolutions Cloud n'est pas supprimé, mais les utilisateurs n'y ont plus accès.</td><td>Le propriétaire devra transférer la propriété à un autre utilisateur et attendre que le Devolutions Cloud soit supprimé avant que le Devolutions Account puisse être supprimé.</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/fr/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.