> 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/web-interface/administration/management/users/administrator-invite.md).

# Invitation af administrator

Inviter en ny administrator til Devolutions Cloud via e-mail, knyt eller opret vedkommendes Devolutions Account, og tildel administratorrettigheder.

Administratorer kan invitere bestemte brugere til at blive administrator af Devolutions Cloud. Vi anbefaler kraftigt, at De inviterer mindst én anden administrator.

1. Gå til ***Administration – Brugere***.
2. Klik på ***Tilføj administrator***.
3. Skriv administratorens e-mailadresse.
4. Tryk på Enter.

Dette trin kontrollerer, om brugeren har en Devolutions Account.

Hvis det er tilfældet, knyttes kontoen til Devolutions Cloud. Hvis ikke, oprettes der automatisk en Devolutions Account med en ***midlertidig adgangskode***, og De kan vælge, hvordan den skal håndteres. De kan administrere, hvordan ***midlertidige adgangskoder*** håndteres, under ***Administration – Systemindstillinger – Generelt***.

5. Klik på ***Næste***.
6. Vælg yderligere ***indstillinger***.
7. Klik på ***Send invitation***.


---

# 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/web-interface/administration/management/users/administrator-invite.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.