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

# Administrator invite

Invite a new administrator to Devolutions Cloud by email, link or create their Devolutions Account, and assign administrator rights.

Administrators can invite specific users to become administrator of the Devolutions Cloud. We strongly recommend that you invite at least one other administrator.

1. Go to ***Administration – Users***.
2. Click ***Add Administrator***.
3. Type the administrator's email address.
4. Press Enter.

This step will validate if the user has a Devolutions Account.

If they do, it will link the account to Devolutions Cloud. If not, it will automatically create a Devolutions Account with a ***Temporary Password***, which you can choose how to handle. You can manage how ***Temporary Passwords*** are handled in ***Administration – System Settings – General***.

5. Click ***Next***.
6. Select additional ***Options***.
7. Click ***Send Invite***.


---

# 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/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.