> 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/server/da/knowledge-base/how-to-articles/offboard-users-from-devolutions-server.md).

# Fjern brugere fra Devolutions Server

Fjern brugere fra Devolutions Server ved at overføre deres boks til en delt boks og automatisk fjerne deres licenstildeling under sletningen.

Når en bruger slettes i Devolutions Server, kan brugerens brugerboks overføres til en delt boks, så alle poster bevares til fortsat brug i organisationen. Processen sikrer, at ingen kritiske data går tabt under fjernelsen. Derudover fjernes licenser, der er tildelt den slettede bruger, automatisk, hvilket forenkler administrationen af licenser.

1. Åbn Devolutions Server.
2. Gå til ***Administration - Brugere***.
3. Klik på ***Mere*** (ikonet ***...***) ud for den bruger, De vil slette.
4. Vælg ***Slet***.
5. Klik på ***Send til listen over slettede brugere***.


---

# 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/server/da/knowledge-base/how-to-articles/offboard-users-from-devolutions-server.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.