> 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/knowledge-base/how-to-articles/migrate-from-security-groups-legacy-to-user-groups.md).

# Migrate from security groups legacy to user groups

Migrate from deprecated legacy Security Groups to User Groups Based Access Control for more granular security in Remote Desktop Manager.

{% hint style="danger" %}
Security groups and legacy security have been deprecated and will be completely removed starting with version 2023.3 of Remote Desktop Manager.
{% endhint %}

In Remote Desktop Manager, the access to your objects can be secured and managed using the \*\*\*User Groups Based Access Control\*\*\*. This type of security gives you a more granular control over your security.

{% hint style="info" %}
For more information, please refer to [User Groups Based Access Control](/rdm/user-group-based-access-control.md).
{% endhint %}

### Migrating to User Groups

1. Open Remote Desktop Manager.
2. Under ***Administration – Management***, click on ***User Groups***.
3. Create and apply the groups.
4. Click on the ***Security Groups (Legacy)*** button in the ***Management*** section.
5. Delete every security group by selecting each one and clicking on ***Delete Security Group***.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>To manage your user's permissions, we recommend you switch from <em><strong>Security Groups</strong></em> (deprecated) to <a href="/rdm/user-group-based-access-control/permissions.md">Permissions</a>. Once the migration is done, <a href="/rdm/knowledge-base/how-to-articles/disable-legacy-security-in-remote-desktop-manager.md">disable legacy security</a>.</p></div>


---

# 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/knowledge-base/how-to-articles/migrate-from-security-groups-legacy-to-user-groups.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.