> 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/how-to-filter-tasks.md).
# How to filter tasks
### Filtering tasks in the overview
Inside the Tasks overview, there are pre-made filters ready, allowing users to quickly access specific task lists without the need to set up manual filters each time.
You can also use column headers in the task overview table to define any specific filter values.
{% hint style="info" %}
**Tip** To read about how to search more effectively, read here: [Search help](/reference/pim/search/search-help.md)
{% endhint %}
The tasks overview page where the pre-made filters are placed.
### Filtering tasks in the side menu
In the side menu, you can filter tasks by 'Assigned to me' or 'Created by me'. Inside each tab you can also choose between 'Open tasks' or 'All tasks'. For additional filtering options, please refer to the Tasks overview.
The tasks side-menu and its filters.
---
# 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.struct.com/tutorials/guides/how-to-use-tasks/how-to-filter-tasks.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.