> 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/ribbon-menu-bar/administration/user-management/user-types.md).

# Brugertyper

Forstå brugertyperne Administrator, Bruger og Kontraktør i Remote Desktop Manager og de grundlæggende rettigheder, der tildeles hver type, når der oprettes brugere.

Når der oprettes brugere i Remote Desktop Manager, er tre brugertyper tilgængelige. Grundlæggende rettigheder tildeles de oprettede brugere afhængigt af deres type.

| Type          | Beskrivelse                                                                    |
| ------------- | ------------------------------------------------------------------------------ |
| Administrator | Tildel alle rettigheder og tilladelser til brugeren.                           |
| Bruger        | Tildel alle de grundlæggende rettigheder til brugeren (Tilføj, Rediger, Slet). |
| Kontraktør    | Tildel midlertidige, brugerdefinerede rettigheder til eksterne brugere.        |

## Rettigheder

Når en bruger sættes til brugertypen ***Kontraktør***, skal rettigheder tildeles manuelt. Disse rettigheder har umiddelbar indflydelse på, hvilke handlinger brugeren kan udføre på usikrede poster. Derfor skal der tildeles rettigheder, for at brugerne kan udføre handlinger på poster, da tilladelser ikke kan tilsidesætte fraværet af en rettighed.\
\
Når rettighederne er tildelt, kan de begrænses ved hjælp af [Sikkerhed baseret på brugergrupper](/rdm/da/user-group-based-access-control.md).\
\
Rettigheden ***Tilføj*** viser også valgmuligheden ***Tilføj i boks***. Den skal være aktiveret, for at brugerne kan tilføje poster i arbejdsområdets boksmappe.


---

# 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/ribbon-menu-bar/administration/user-management/user-types.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.