> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/tasks/filtering.md).
# Filtering
Filters are a great resource to keep track of all tasks assigned.
Once tasks are assigned and the ball is rolling, you'll want to use filters to make sure you can keep track of all of the tasks assigned. You can adjust filters and your view at the top of this page, see below:
The first way to filter your tasks is based on due date, the type of task, the title, and when it was created. If this isn't what you are looking for, navigate to the upside down triangle by the green + button to see more options, shown below.
Here you can filter by who is responsible, the status of the task, and who created the task. Ultimately, it's up to you how you want to filter your page, but with these options you should have everything you need.
---
# 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://help.gleantap.com/tasks/filtering.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.
