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

# User types

Understand the Administrator, User, and Contractor user types in Remote Desktop Manager and the basic rights granted to each when creating users.

When creating users in Remote Desktop Manager, three types of user are available. Basic rights are granted to the created users depending on their type.

| Type          | Description                                                 |
| ------------- | ----------------------------------------------------------- |
| Administrator | Grant all rights and permissions to the user.               |
| User          | Grant all the basic rights to the user (Add, Edit, Delete). |
| Contractor    | Grant temporary, custom rights for external users.          |

## Rights

When setting a user to the ***Contractor*** user type, rights must be granted manually. These rights have an immediate influence on which actions the user can perform on unsecured entries. Therefore, rights must be granted for users to be able to perform actions on entries, as permissions cannot override the absence of right.\
\
Once rights are granted, they can be restricted using [User groups-based security](/rdm/user-group-based-access-control.md).\
\
The ***Add*** right also displays the ***Add in vault*** option. This must be enabled for users to be able to add entries into the vault folder of the workspace.


---

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