> 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/powershell-universal/da/apps/role-based-access.md).

# Rollebaseret adgang

Begræns PowerShell Universal-apps og -sider efter rolle, og brug variablen Roles til betinget at vise komponenter baseret på brugerens rollemedlemskab.

## App-roller

Når appgodkendelse er aktiveret, kan De definere den rolle, som en bruger skal være en del af for at få adgang til dashboardet. Roller konfigureres under **Secure > Roles** eller fra konfigurationsfilen `roles.ps1`.

Hvis en bruger forsøger at besøge en app, som vedkommende ikke har adgang til, vises en Not Authorized-side.

## Sideroller

De kan også vise eller skjule sider baseret på roller. For at definere en rolle for en side skal De bruge parameteren `-Role` på `New-UDPage`. Kun brugere med den angivne rolle har adgang til denne side.

```powershell
New-UDPage -Role 'Administrators' -Content {
    New-UDTypography -Text 'Admins only'
}
```

## $Roles-variabel

Ud over app- og sideroller kan De også kontrollere, hvilke roller en bruger er en del af, ved hjælp af variablen `$Roles`, der er tilgængelig i Apps. Denne variabel indeholder et array med de roller, der er tildelt brugeren.

De kunne for eksempel vise knappen `Restart-Computer` kun for administratorer.

```powershell
if ($Roles -contains "Administrator") {
    New-UDButton -Text 'Restart Server' -OnClick {
        Restart-Computer
    }
}
```

### Se også

* [Devolutions Academy – Oversigt og godkendelse](https://academy.devolutions.net/student/activity/3542770-part-1-outline-and-authentication)


---

# 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/powershell-universal/da/apps/role-based-access.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.