> 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/web-interface/utilities/reports/vault-workspace-and-redundant-role-assignments-reports.md). # Vault, Workspace, and redundant role assignments reports View vault, workspace, and redundant role assignment reports in Devolutions Server, and remove overlapping role grants. ### Vault role assignments The ***Vault role assignments*** report displays role assignments scoped to vaults. Each row shows the user the role is assigned to, the role itself, the vault it applies to, its scope, and how it was asigned to the user. ### Workspace assignments The ***Workspace role assignments*** report consists of a list of the user with roles assigned to them. The columns display each user along with their roles – and how they got them –, and whether or not the roles are limited to vaults the user has access to. ### Redundant role assignments The ***Redundant role assignments*** report lists all the roles assigned to users that give the same permissions. Click ***Remove all redundant*** to safely take away useless roles from users. --- # 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/web-interface/utilities/reports/vault-workspace-and-redundant-role-assignments-reports.md?ask=&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.