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

# Dar de baja usuarios de Devolutions Server

Desvincule usuarios de Devolutions Server transfiriendo su bóveda a una bóveda compartida y desasignando automáticamente su licencia durante la eliminación.

Cuando se elimina un usuario en Devolutions Server, su bóveda de usuario puede transferirse a una bóveda compartida, lo que garantiza que todas las entradas se conserven para que la organización pueda seguir utilizándolas. Este proceso garantiza que no se pierda ningún dato crítico durante la desvinculación. Además, las licencias asignadas al usuario eliminado se desasignan automáticamente, lo que simplifica el proceso de gestión de licencias.

1. Abra Devolutions Server.
2. Vaya a ***Administración - Usuarios***.
3. Haga clic en ***Más*** (icono ***...***) junto al usuario que desea eliminar.
4. Seleccione ***Eliminar***.
5. Haga clic en ***Enviar a la lista de usuarios eliminados***.


---

# 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 dynamically 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/es/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 `build a script that syncs our docs to a CMS` 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.