> 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/rdm/es/knowledge-base/how-to-articles/disable-legacy-security-in-remote-desktop-manager.md).

# Desactivar la seguridad heredada en Remote Desktop Manager

Desactive la seguridad heredada y los grupos de seguridad en Remote Desktop Manager después de migrar primero los permisos existentes a los grupos de usuarios.

{% hint style="danger" %}
La seguridad heredada y los grupos de seguridad están obsoletos y se eliminarán por completo a partir de la versión 2023.3 de Remote Desktop Manager.Antes de desactivar la seguridad heredada, se recomienda configurar los ***Grupos de usuarios***. Consulte [Migrar de grupos de seguridad a grupos de usuarios](https://docs.devolutions.net/rdm/es/knowledge-base/how-to-articles/migrate-from-security-groups-legacy-to-user-groups.md).
{% endhint %}

Siga los pasos siguientes para desactivar la ***Seguridad heredada*** en Remote Desktop Manager.

1. Vaya a la pestaña ***Administración*** en Remote Desktop Manager.
2. En la sección ***Configuración***, seleccione ***Configuración del sistema***.
3. Vaya a ***Gestión de bóvedas – Configuración de seguridad – Seguridad*** y desactive ***Usar seguridad heredada***.
4. Haga clic en ***Ok*** para aplicar los cambios y cerrar la ventana.


---

# 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/rdm/es/knowledge-base/how-to-articles/disable-legacy-security-in-remote-desktop-manager.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.
