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

# Migrer fra ældre sikkerhedsgrupper til brugergrupper

Migrer fra forældede ældre sikkerhedsgrupper til brugergruppebaseret adgangskontrol for mere detaljeret sikkerhed i Remote Desktop Manager.

{% hint style="danger" %}
Sikkerhedsgrupper og ældre sikkerhed er blevet forældede og fjernes helt fra og med version 2023.3 af Remote Desktop Manager.
{% endhint %}

I Remote Desktop Manager kan adgangen til Deres objekter sikres og administreres ved hjælp af \*\*\*Brugergruppebaseret adgangskontrol\*\*\*. Denne type sikkerhed giver Dem en mere detaljeret kontrol over Deres sikkerhed.

{% hint style="info" %}
Se [Brugergruppebaseret adgangskontrol](/rdm/da/user-group-based-access-control.md) for at få flere oplysninger.
{% endhint %}

### Migrering til brugergrupper

1. Åbn Remote Desktop Manager.
2. Under ***Administration – Styring*** skal De klikke på ***Brugergrupper***.
3. Opret og anvend grupperne.
4. Klik på knappen ***Sikkerhedsgrupper (ældre)*** i afsnittet ***Styring***.
5. Slet hver sikkerhedsgruppe ved at vælge hver enkelt og klikke på ***Slet sikkerhedsgruppe***.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>For at administrere Deres brugers tilladelser anbefaler vi, at De skifter fra <em><strong>Sikkerhedsgrupper</strong></em> (forældet) til <a href="/rdm/da/user-group-based-access-control/permissions.md">Tilladelser</a>. Når migreringen er færdig, skal De <a href="/rdm/da/knowledge-base/how-to-articles/disable-legacy-security-in-remote-desktop-manager.md">deaktivere ældre sikkerhed</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/da/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.
