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

# Permission issues

Remote Desktop Manager permissions not being enforced are fixed by checking user types, user group assignments, and folder permission inheritance settings.

Despite having configured your permissions (whether set through inheritance or with custom permissions) you may find they are not properly enforced.

### Solution 1

When creating users, make sure that their user type are set to ***User***.

{% hint style="info" %}
User types of existing users can be consulted at any time in ***Administration*** – ***Users*** , under the ***User Type*** column.
{% endhint %}

### Solutions 2

Often, users are created and not given permissions directly, but are instead added to user groups that have those permissions. To check if this is the case, go to ***Administration*** – ***Users***, and consult the ***User Groups*** column. You can then [reassign users to different user groups or remove them](/rdm/user-group-based-access-control.md) as needed.

### Solution 3

If permissions are enforced for everything but a subset of entries, it may be that those entries inherit their permissions from a parent folder which does not inherit its own permissions from the vault settings.

To remedy this, right-click on the parent folder, go to ***Properties*** – ***Security*** – ***Permissions*** and make sure the permission is set to ***Inherited***.


---

# 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/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.