> 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/password-management.md).

# Password management

Devolutions Cloud password management centralizes credentials in shared vaults with password policies, a generator, and role-based access control.

Password management in Devolutions Cloud centralizes credentials, secrets, and access policies in shared vaults instead of scattered personal password stores. Entries can store website logins, server and application accounts, API keys, or one-time passwords and link them directly to remote sessions or other resources.

Combined with password policies and the built-in generator, administrators can enforce complexity and uniqueness requirements while roles and permissions control who can view, use, or update each secret. A common approach is to keep admins' privileged accounts in a restricted-access vault and let users launch connections from Remote Desktop Manager or Devolutions Password Manager without ever seeing the underlying passwords.

#### Related topics

* [Password policies](/cloud/web-interface/administration/management/password-policies.md)
* [Password generator](/cloud/web-interface/administration/management/password-generator.md)
* [Create and manage vaults](/cloud/web-interface/administration/management/vaults/create-and-manage-vaults.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/password-management.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.