> 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/da/knowledge-base/knowledge-base-articles/devolutions-cloud-account-deletion.md).

# Sletning af en Devolutions Cloud-konto

Lær, hvordan De sletter en konto i Devolutions Cloud fra Devolutions Portal, og hvilken tidslinje for meddelelser der gælder før den endelige sletning.

Hvis De er ejer af en konto i Devolutions Cloud og vil slette den, skal De logge på Devolutions Portal og åbne sektionen ***Produkter***. Klik på de tre prikker (indstillingsmenuen) ved siden af kontoen i Devolutions Cloud, og vælg derefter ***Slet***.

Når kontoen i Devolutions Cloud slettes, forbliver det tilknyttede domæne reserveret i 30 dage.

Sletningen sættes i gang, når alle licenser er udløbet, og Devolutions Cloud har været inaktiv i tre år i træk.

* **30 dage før sletning**: Der sendes en e-mail med en meddelelse til alle administratorer.
* **1 dag før sletning**: Der sendes en påmindelse med e-mail til alle administratorer.
* **På sletningsdagen**: Devolutions Cloud slettes.


---

# 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/da/knowledge-base/knowledge-base-articles/devolutions-cloud-account-deletion.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.