> 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/contractor-user-invite.md).

# Contractor user invite

Invite contractor users to Devolutions Cloud with restricted, read-only PAM access, mandatory expiration dates, and compact mode display.

Contractor users have limited access to resources, automatically expire at a set date, must provide an email address, and are required to enter a password upon login. This user type comes in handy for managing external Devolutions Cloud users.

Although Contractor users have access to [PAM capabilities](https://docs.devolutions.net/pam/pam-with-devolutions-server), they are restricted to ***Read-only*** mode. Follow the steps below to invite a contractor.

1. In Devolutions Cloud, go to ***Administration*** – ***General*** – ***Access & authentication*** and toggle ***Contractor***.
2. Then, head to ***Administration*** – ***Users*** and click the ***Add*** button (***+***). Select ***Add contractor***
3. Follow the steps displayed in the Devolutions Cloud user interface. Note that an expiration date is mandatory for contractor users.
4. Click ***Send invite*** to finalize the process. The future user will then receive an email inviting them to connect using a temporary password.

### Switching to compact mode

Since the contractor user type is designed for external users, we have added a simplified display only showing the available sessions. To switch to it, click your profile icon located at the top right corner of the user interface, and select ***Switch to compact mode (sessions only)***.


---

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