> 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/web-interface/utilities/reports/vault-workspace-and-redundant-role-assignments-reports.md).

# Informes de bóveda, Workspace y asignaciones de roles redundantes

Consulte los informes de asignaciones de roles de bóveda, workspace y redundantes en Devolutions Server, y elimine las concesiones de roles superpuestas.

### Asignaciones de roles de bóveda

El informe ***Asignaciones de roles de bóveda*** muestra las asignaciones de roles cuyo alcance son las bóvedas. Cada fila muestra el usuario al que se le asigna el rol, el rol en sí, la bóveda a la que se aplica, su alcance y cómo se asignó al usuario.

### Asignaciones de Workspace

El informe ***Asignaciones de roles de Workspace*** consiste en una lista de los usuarios con roles asignados. Las columnas muestran cada usuario junto con sus roles – y cómo los obtuvieron –, y si los roles están limitados o no a las bóvedas a las que el usuario tiene acceso.

### Asignaciones de roles redundantes

El informe ***Asignaciones de roles redundantes*** enumera todos los roles asignados a los usuarios que otorgan los mismos permisos. Haga clic en ***Eliminar todos los redundantes*** para quitar de forma segura los roles inútiles de los usuarios.


---

# 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/web-interface/utilities/reports/vault-workspace-and-redundant-role-assignments-reports.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.
