> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/eximee-dashboard/konfiguracja/uprawnienia.md).
# Permissions
User roles loaded during login are mapped to permissions in EximeeDashboard.
## Available permissions
The table below presents the available Eximee Dashboard permissions.
* **feature\_browse\_all\_tasks** - Allows the user to browse all tasks in the system,
* **feature\_show\_user\_task\_details** - Allows the user to view task details,
* **feature\_show\_process\_details\_tab** - Allows the user to display the process details tab,
* **feature\_process\_list** - Allows browsing [the case list](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/eximee-dashboard/konfiguracja/lista-spraw.md),
* **feature\_change\_assignee** - Allows the user to release the task (change assignment), if it will still be possible to take it after release,
* **feature\_process\_start** - Allows the user to start a process and see the "Start case" option in the eximee-dashboard side menu,
* **feature\_show\_process\_overview\_tab**- Allows the user to display the process overview,
* **feature\_change\_process\_priority** - Allows the case priority to be modified,
* **feature\_change\_assignee\_to\_another\_user** - Allows the user to change the users assigned to tasks,
* **feature\_browse\_process\_history** *-* Allows the user to browse the case history,
* **feature\_export\_task\_list -** Allows exporting the task list (only for the list in legacy mode),
* **feature\_verify\_client** - Allows displaying the client verification tab using mDowód with the mObywatel app,
* **feature\_resign\_process -** Allows the user to invoke the process resignation action,
* **feature\_browse\_notes -** Allows browsing notes.
* **feature\_add\_notes -** Allows adding notes.
* **feature\_delete\_notes -** Allows deleting notes.
* **feature\_modify\_notes -** Allows modifying notes
* **feature\_config\_edit -** Allows modifying business application configurations in Eximee Dashboard.
{% hint style="info" %}
Permissions for the tab `Notes` describes the page [Notes](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/eximee-dashboard/konfiguracja/notatki.md).
{% endhint %}
## Permission configuration
We configure permissions for a role in the settings of the LAN package.
The parameter used for this is
```
AUTH_ROLE_MAPPING
```
and its value is the comma-separated permissions for individual roles.
```
Rola1:uprawnienie,Rola1:inneUprawnienie,Rola2:uprawnienie
```
## Configuration of groups for User Tasks
For a user with a given role to be able to take a given Task (user-task **from the task list** in Eximee Dashboard), they must have this role defined in the field **candidateGroups**. The value of this field is a comma-separated list containing the names of roles that are to be authorized to take the task. This can be done in the process editor in Eximee Designer by clicking the tile of interest\
User Task -> **User assignment**.
## Role permissions for case types
To make the appropriate case types available to a user with a given role, i.e. processes created based on process definitions, you need to configure role-to-process mapping (i.e. to process definition names).
For this, we configure the parameter
```
PROCESS_DEFINITION_KEY_MAPPING
```
by providing a comma-separated list
```
Rola1:Proces1,Rola2:Proces1,Rola3:Proces2
```
{% hint style="info" %}
For a given request (task) to be visible in Eximee Dashboard, it is enough to set the appropriate value in **candidateGroups**.
For a process to be visible in the case list, you need to set the appropriate mapping of the user's role in **PROCESS\_DEFINITION\_KEY\_MAPPING .** You also need to map the role **feature\_process\_list** to the user's role in the AUTH\_ROLE\_MAPPING parameter
{% endhint %}
---
# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/eximee-dashboard/konfiguracja/uprawnienia.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.
