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

# Rapporter om boks, arbejdsområde og redundante rolletildelinger

Vis rapporter om boks, arbejdsområde og redundante rolletildelinger i Devolutions Server, og fjern overlappende rolletildelinger.

### Rolletildelinger for bokse

Rapporten ***Rolletildelinger for bokse*** viser rolletildelinger, der er afgrænset til bokse. Hver række viser den bruger, rollen er tildelt, selve rollen, den boks den gælder for, dens omfang, og hvordan den blev tildelt brugeren.

### Tildelinger for arbejdsområde

Rapporten ***Rolletildelinger for arbejdsområde*** består af en liste over brugeren med de roller, der er tildelt. Kolonnerne viser hver bruger sammen med rollerne, og hvordan de blev tildelt, samt om rollerne er begrænset til de bokse, brugeren har adgang til.

### Redundante rolletildelinger

Rapporten ***Redundante rolletildelinger*** viser alle de roller, der er tildelt brugere, og som giver de samme tilladelser. Klik på ***Fjern alle redundante*** for sikkert at fjerne unyttige roller fra brugerne.


---

# 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/da/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.