> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/tasks.md).

# Tasks

The tasks dashboard shows an overview of all tasks that are currently assigned to you and that have been completed. If you have the role Platform Administrator you will also see a tab to view all tasks in AppControl.

Tasks enable you to manage recurring (or one-off) activities that are needed to manage your Mendix apps. For example: renewing certificates, renewing functional accounts, collecting information for audit reports, or checking who has access to your app.

Before a task can be assigned it has to be configured. Task templates are managed from the Administration > Tasks page. For more information on how to configure task templates see the [tasks administration](https://docs.bluestorm.io/administration/tasks.md) page in this documentation.

Once a task template has been configured it can be assigned. To assign a task select the 'task assignments' tab and click on 'assign new task'. See the [task assignnment](https://docs.bluestorm.io/dashboards/tasks/task-assignment.md) page for details.

After a task has been assigned AppControl will create a task for each app that the task is assigned to, and will notify the persons responsible. Assigned tasks show up in the task dashboard. To view the current status of a task and to complete it click on it from the overview. See the [task details](https://docs.bluestorm.io/dashboards/tasks/task-details.md) page for more information.


---

# 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.bluestorm.io/dashboards/tasks.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.
