> 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/lista-zadan.md).
# Task list
## Configuration of request visibility on the task list
In order for requests to be visible on the task list, permissions for the user role must be configured: [Permission configuration for the user role (assigning a group in the User Task)](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/eximee-dashboard/konfiguracja/uprawnienia.md).
## Configuration of data displayed in the tile
It is possible to configure the data displayed in the middle part of the tile on the task list in Eximee Dashboard, located e.g. at:
```
ROUTER_HOST:8083/router-ui/#/tasks
```
To configure which data we want to display in the middle part of the tile, in the BPMN process go to:
User task (**UserTask**) → section \***Inputs**.
Add a new parameter named **TASK\_DASHBOARD** and set the variable type (Variable Assignment Type) to **Map**.
Figure 1. User task configuration "UserTask"
After clicking **+** we can add a label-value configuration that will be displayed on the task list in Eximee Dashboard.
Remember that the values in the field **Key** must be unique for a given user task (*UserTask*).
In the field **Value** literals or task variables can be placed using;
```
${NAZWA_ZMIENNEJ}
```
To retrieve global variables (this can be done using [*scriptTask*](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/zadania-automatyczne/zadanie-skryptowe-bpms-scripttask.md)) of the process, use the method **getVariable**:
```js
${execution.getVariable("variable_name e.g. start.documentId")}
```
Example of the configured list:
Figure 2. Task list
We can also determine the order of the displayed variables by providing, at the beginning of the key, a number in square brackets on the basis of which the variables will be sorted, e.g. "\[1]Label". Such a number will not be displayed, and variables without a number will go to the very end. For example, the map:
```js
execution.setVariable("TASK_DASHBOARD", [
"[3]A": "A",
"B": "B",
"[1]C": "C"
]);
```
will be displayed as key-value pairs in the order of labels C, A, B.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/eximee-dashboard/konfiguracja/lista-zadan.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.