> 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/troubleshooting-articles/permission-issues.md).

# Problemer med tilladelser

Tilladelser i Remote Desktop Manager, der ikke håndhæves, rettes ved at kontrollere brugertyper, tildelinger af brugergrupper og indstillinger for nedarvning af mappetilladelser.

Selvom De har konfigureret Deres tilladelser (uanset om de er angivet via nedarvning eller med brugerdefinerede tilladelser), kan De opleve, at de ikke håndhæves korrekt.

### Løsning 1

Når De opretter brugere, skal De sørge for, at deres brugertype er sat til ***Bruger***.

{% hint style="info" %}
Brugertyper for eksisterende brugere kan til enhver tid ses under ***Administration*** – ***Brugere*** , i kolonnen ***Brugertype***.
{% endhint %}

### Løsninger 2

Ofte oprettes brugere uden at få tilladelser direkte, men tilføjes i stedet til brugergrupper, der har disse tilladelser. For at kontrollere, om det er tilfældet, skal De gå til ***Administration*** – ***Brugere*** og se kolonnen ***Brugergrupper***. De kan derefter [omfordele brugere til andre brugergrupper eller fjerne dem](/rdm/da/user-group-based-access-control.md) efter behov.

### Løsning 3

Hvis tilladelser håndhæves for alt undtagen en delmængde af poster, kan det være, at disse poster nedarver deres tilladelser fra en overordnet mappe, som ikke selv nedarver sine tilladelser fra boksindstillingerne.

For at afhjælpe dette skal De højreklikke på den overordnede mappe, gå til ***Egenskaber*** – ***Sikkerhed*** – ***Tilladelser*** og sørge for, at tilladelsen er sat til ***Nedarvet***.


---

# 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/troubleshooting-articles/permission-issues.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.