> For the complete documentation index, see [llms.txt](https://docs.growthfactor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growthfactor.ai/manage/filters.md).
# Filters
List & library filters narrow what you *see* across your dashboard pages — deals, sites, files, maps, layers, and Market Planning studies — by workspace, type, and sort order.
***
## List & Library Filters
{% columns %}
{% column valign="middle" %}
Most dashboard pages share a single **Filter** menu for narrowing long lists. Look for the **Filter** button (funnel icon) at the top right of the page — it appears on **Deals, Sites, Files, Maps, Layers,** and **Market Planning studies**.
The button shows a badge with the number of filters currently applied, so you can tell at a glance when a list is narrowed.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### What's in the menu
The menu combines every way to narrow a list in one place. Each page shows only the sections that apply to it:
* **Show** — limit the list by type or scope (for example, **My Layers** or **Workspace Layers** on the Layers view)
* **Sort by** — order the list (for example, **Newest first**, **Oldest first**, or **Alphabetical**)
* **Workspaces** — scope the list to one or more workspaces. The workspace tree mirrors your hierarchy, so you can include a parent and its sub-workspaces together. A count next to each workspace shows how many matching items it holds
### Resetting
Click **Reset** at the top of the menu to clear every applied filter at once and return the list to its default view.
---
# 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.growthfactor.ai/manage/filters.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.
