> 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/concepts/basic-concepts/user-management.md). # User management Devolutions Cloud user management covers inviting users by email, creating user groups, and assigning roles that control vault and application access. User management in Devolutions Cloud covers how administrators invite people, group them, and assign roles so each user has the right level of access. From the Administration – Users and User groups sections, you can invite users by email, map them to groups coming from SSO, and apply roles that grant system permissions as well as access to specific vaults. Temporary passwords and ownership options help bootstrap new administrators safely, while companion tools access decides which clients, such as Remote Desktop Manager or Devolutions Password Manager, they may use. As an example, you might create a Service desk user group, assign it a role with read-only access to production vaults, and then invite analysts into that group so their access is ready on first login. #### Related topics * [Create and invite users](/cloud/web-interface/administration/management/users/create-and-invite-users.md) * [Create and manage user groups](/cloud/web-interface/administration/management/user-groups/create-and-manage-user-groups.md) * [Invite users in Devolutions Cloud](/cloud/getting-started/get-started-with-devolutions-cloud/invite-users-to-devolutions-cloud.md) --- # 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/concepts/basic-concepts/user-management.md?ask=&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.