> 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/cloud/da/knowledge-base/how-to-articles/assign-roles-and-permissions.md).

# Tildel roller og tilladelser

Tildel roller og tilladelser i Devolutions Cloud på post-, mappe-, boks- eller globalt niveau for at styre præcis, hvad hver bruger kan få adgang til.

Roller og tilladelser kan tildeles i Devolutions Cloud for hvert niveau ved at følge nogle få enkle trin.

Hvis De vil redigere roller og tilladelser i en bestemt post eller mappe, skal De klikke på ellipseknappen ved siden af et postnavn.

Administratorer kan også gå til ***Administration*** – ***Bokse*** og klikke på ikonet ***Rediger*** ved siden af boksen for at ændre den.

Uanset hvilken sti De vælger, bør det samme vindue ***Boks*** vises. Vælg sektionen ***Sikkerhed***, og klik på fanen ***Rediger*** for at administrere roller og tilladelser.

#### Globale roller og tilladelser

Hvis De vil redigere globale roller og tilladelser, skal De gå til sektionen ***Administration***, som findes under ***System*** i sidemenuen, og derefter klikke på ***Systemtilladelser***.

Klik derefter på ikonet ***Rediger***.


---

# 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/cloud/da/knowledge-base/how-to-articles/assign-roles-and-permissions.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.