> 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/es/concepts/intermediate-concepts/password-policies.md).

# Políticas de contraseñas

Las políticas de contraseñas de Devolutions Server definen reglas reutilizables de longitud y conjuntos de caracteres que el generador de contraseñas aplica al crear credenciales.

Las políticas de contraseñas de Devolutions Server definen reglas reutilizables para generar contraseñas que cumplan la política de seguridad de su organización. Las políticas controlan la longitud, los conjuntos de caracteres y requisitos especiales como evitar caracteres similares o imponer estilos de frase de contraseña.

Cuando los usuarios crean o rotan una entrada de credencial, el generador de contraseñas utiliza estas políticas para que las contraseñas sean seguras y coherentes en todas las bóvedas. Un administrador podría, por ejemplo, configurar políticas más estrictas para cuentas privilegiadas que para aplicaciones empresariales estándar, y recurrir a Remote Desktop Manager o Devolutions Password Manager para inyectar esas contraseñas sin exponerlas.

#### Temas relacionados

* [Políticas de contraseñas](/server/es/web-interface/administration/templates/password-policies.md)
* [Configuración del sistema](/server/es/web-interface/administration/configuration/system-settings.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/es/concepts/intermediate-concepts/password-policies.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.