> 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/rdm/es/ribbon-menu-bar/administration/system-settings/vault-management.md).

# Gestión de bóvedas

Configure los valores predeterminados de las bóvedas para todo el espacio de trabajo en la Configuración del sistema de Remote Desktop Manager, incluidas la visibilidad, los permisos predeterminados y

La sección Gestión de bóvedas de la Configuración del sistema controla el comportamiento de las bóvedas y los valores predeterminados de acceso en todo el espacio de trabajo. Los administradores pueden configurar la visibilidad predeterminada de las bóvedas (pública o privada), definir los [permisos predeterminados](/rdm/es/ribbon-menu-bar/administration/system-settings/vault-management/default-permissions.md) que se aplican a todas las bóvedas y gestionar los [conjuntos de permisos](/rdm/es/ribbon-menu-bar/administration/system-settings/vault-management/permission-sets.md), que son agrupaciones reutilizables de permisos, como los conjuntos integrados Lector, Operador y Colaborador, que pueden concederse a usuarios y grupos de usuarios de forma masiva.


---

# 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/rdm/es/ribbon-menu-bar/administration/system-settings/vault-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.