> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-tasks.md).

# How to use Tasks

Tasks make it possible to structure and track progress inside the PIM.

### What are Tasks?

Tasks are essential for delegating work and tracking progress within the PIM. Each task can involve various entities, such as [products](/fundamental-concepts/data-management.md), [categories](/fundamental-concepts/data-model.md), variant groups, [variants](/fundamental-concepts/data-management.md), assets, and [global list values](broken://pages/33UGJbwodzi2bP6o2PZJ). Multiple entities can be associated with a single task.

Tasks can be assigned to individual users or user groups. To access Tasks, use the pop-up window from the top right navigation menu or click 'Tasks' in the menu and select 'Go to task overview' for a detailed view.

{% embed url="<https://vimeo.com/1109934319/db2d7dda38>" %}
Task assignment in Struct PIM (duration 6:00)
{% endembed %}

### Guides covering Tasks

* [How to set up and edit a task](/tutorials/guides/how-to-use-tasks/how-to-set-up-and-edit-a-task.md)
* [How to assign a task](/tutorials/guides/how-to-use-tasks/how-to-assign-a-task.md)
* [How to add and handle attached entities for a task](/tutorials/guides/how-to-use-tasks/how-to-add-and-handle-attached-entities-for-a-task.md)
* [How to use comments on a task](/tutorials/guides/how-to-use-tasks/how-to-use-comments-on-a-task.md)
* [How to filter tasks](/tutorials/guides/how-to-use-tasks/how-to-filter-tasks.md)
* [How to filter tasks](/tutorials/guides/how-to-use-tasks/how-to-filter-tasks.md)


---

# 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.struct.com/tutorials/guides/how-to-use-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.