> 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/account-menu/my-roles.md).

# My roles

View your own role assignments in Devolutions Server, including their scope   and how each one was granted.

The ***My roles*** section lists every role assigned to you, across all three scopes: ***Workspace***, ***Vault***, and ***PAM provider*** along with how each one was granted.

To view your roles, click your avatar in the top-right corner of the Web interface and select ***My roles***.

<table><thead><tr><th width="180">Text</th><th>Description</th></tr></thead><tbody><tr><td><strong>Role</strong></td><td>Name of the assigned role along with a short description.</td></tr><tr><td><strong>Scope</strong></td><td>Where the role applies: the workspace as a whole, a specific vault, or a PAM provider.</td></tr><tr><td><strong>Assigned via</strong></td><td>How you received the role.</td></tr></tbody></table>

{% hint style="info" %}
This page is read-only. To request a change to your roles, contact your Devolutions Server administrator.
{% endhint %}

**See also**

* [Role assignments](/server/web-interface/administration/configuration/system-permissions.md)
* [Workspace and redundant role assignments](/server/web-interface/utilities/reports/vault-workspace-and-redundant-role-assignments-reports.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/web-interface/account-menu/my-roles.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.