> 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/rdm/fr/concepts/intermediate-concepts/tasks.md).

# Tâches

Créez des listes de tâches dans Remote Desktop Manager pour organiser les étapes récurrentes de maintenance, d'audit et d'intégration liées aux entrées de connexion.

Une tâche est un rappel d'exécuter une affectation ou un ensemble d'actions précis; les listes de tâches offrent une façon structurée d'organiser, de suivre et de terminer le travail.

Dans Remote Desktop Manager, créez une liste de tâches pour regrouper les étapes récurrentes de maintenance, d'audit ou d'intégration. Ajoutez des dates d'échéance, une priorité et des notes, et liez les tâches à des entrées de connexion dans un coffre. Cela accroît la visibilité, normalise les processus et aide les équipes à terminer le travail à temps sans disperser les rappels dans plusieurs outils.

#### Sujets connexes

* [Tâche](/rdm/fr/ribbon-menu-bar/window/task.md)
* [Liste de tâches](/rdm/fr/ribbon-menu-bar/view/task-list.md)

#### Voir aussi :

* [Devolutions Academy - Breaking down common scenarios: daily task efficiency](https://academy.devolutions.net/student/activity/3380811-breaking-down-common-scenarios-daily-task-efficiency)


---

# 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/rdm/fr/concepts/intermediate-concepts/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.