> 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.md). # Management Manage day-to-day Devolutions Cloud resources, including application identities, users, vaults, password rules, licenses, and entry templates. This section covers the resources you manage day-to-day in a Devolutions Cloud workspace. [Application identities](/cloud/web-interface/administration/management/application-identities.md) handles creating service accounts for connecting external tools like the Devolutions.PowerShell module to the workspace, while [User groups](/cloud/web-interface/administration/management/user-groups.md) and [Users](/cloud/web-interface/administration/management/users.md) take care of inviting and organizing the people who have access, including administrator rights, temporary passwords, and offline mode. [Vaults](/cloud/web-interface/administration/management/vaults.md) handles creating, restricting, and restoring the vaults where entries live, [Password generator](/cloud/web-interface/administration/management/password-generator.md) and [Password policies](/cloud/web-interface/administration/management/password-policies.md) set the rules applied to generated and stored passwords, [Licenses](/cloud/web-interface/administration/management/licenses.md) manages registering and assigning product licenses, and [Entry templates](/cloud/web-interface/administration/management/entry-templates.md) provides templates for standardizing new entries. --- # 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.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.