> 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/server/da/concepts/advanced-concepts/permissions-rbac-and-roles.md).

# Tilladelser, RBAC og roller

Tilladelser, RBAC og roller i Devolutions Server definerer detaljerede adgangsrettigheder på boks-, mappe- og postniveau ud fra jobfunktionen.

Tilladelser, RBAC og rollebaseret adgangskontrol (RBAC) i Devolutions Server definerer, hvem der kan se eller ændre systemindstillinger, bokse, mapper og poster. Tilladelser er detaljerede rettigheder som Vis, Rediger eller Vis adgangskode, der anvendes på boks-, mappe- eller postniveau, mens roller grupperer tilladelsessæt, så administratorer kan tildele adgang ud fra jobfunktion i stedet for pr. bruger.

Et typisk design knytter kataloggrupper til roller som Helpdesk, Revisor eller PAM-administrator og lader derefter boksejere bruge disse roller, når de konfigurerer tilladelsessæt. Det holder mindste privilegium håndterbart og sikrer, at ændringer af gruppemedlemskab automatisk slår igennem i adgangen til Devolutions Server.

#### Relaterede emner

* [Tilladelser](/server/da/web-interface/user-group-based-security/permissions.md)
* [Sikkerhed baseret på brugergrupper](/server/da/web-interface/user-group-based-security.md)
* [PAM-tilladelser](https://docs.devolutions.net/pam/pam-with-devolutions-server/pam-permissions)


---

# 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/server/da/concepts/advanced-concepts/permissions-rbac-and-roles.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.