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

# Password management

Password management in Devolutions Server centralizes credentials in shared and personal vaults while enforcing organization wide password policies.

Password management in Devolutions Server centralizes credentials in shared and personal vaults while enforcing organization wide password policies. Administrators configure password templates and rules in System settings, then apply them through the built in password generator so users create strong, compliant passwords directly in entries. The user vault gives each person a private, secure space for their own accounts, which reduces the temptation to use browsers or consumer password tools at work.

For instance, you might require 20 character random passwords for all privileged accounts and rely on Devolutions Password Manager or Remote Desktop Manager to fill them into target systems without revealing them to users.

#### Related topics

* [System settings](/server/web-interface/administration/configuration/system-settings.md)
* [Password policies](/server/web-interface/administration/templates/password-policies.md)
* [User vault](/server/web-interface/user-vault.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/server/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.