> For the complete documentation index, see [llms.txt](https://docs.paledo.de/7doD8BRz3n5IiVGP4B0G/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paledo.de/7doD8BRz3n5IiVGP4B0G/english/modules/aufgaben.md). # Tasks Tasks - also **Orders**, **Processes**, **Notifications** or **Reports -** can be processed in Paledo in many different ways and by different actors. Details on capturing, assigning, scheduling and managing, processing, documenting and analyzing tasks can be found here: ## For planners

Task allocation

Efficient assignment of work tasks (orders, operations, notifications, or reports) via drag & drop, based on availability, qualification, and status with the

Screenshot der Aufgabenverteilung in Paledo-WebScreenshot der Aufgabenverteilung Benutzer in Paledo-Web

Graphical planning board

Visual overview of planned tasks and their management in a calendar view, individually groupable, with configurable color codes for different task types and statuses

Screenshot der Graphischen Plantafel in Paledo-Web

Shift overview

Efficient Deployment control through visualized, category-driven planning and management of shifts and teams

Screenshot der Schichtübersicht in Paledo-Web
*** ## For maintenance technicians and production employees

Tasks

Overview of your open, ongoing, and completed tasks in a filterable list, grouped by orders, operations, notifications and/or reports in the

My processes

Structured overview of your planned or currently being processed operations

Screenshot von Meine Vorgänge in Paledo-Web

My time confirmations

Overview of your time feedback

--- # 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.paledo.de/7doD8BRz3n5IiVGP4B0G/english/modules/aufgaben.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.