> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/end-users/list-view-management/searching-and-filtering-in-list-view.md).
# Searching & Filtering in List View
Quickly locate items by searching the list or applying filters.
## Applying Filters
Use **Quick Filters**, the **Keyword Filter**, or **All Filters** to narrow the list.
### Quick Filters
Use **Quick Filters** at the top of the page to filter the list by key attributes.
* To apply a filter, select a filter chip and specify the criteria in the panel that opens.
* To clear a filter, select the :circle-xmark: on the filter chip or clear the criteria in the panel.
The list updates automatically when you apply, modify, or clear a filter—no page refresh is required.
{% hint style="warning" %}
**Quick Filters** operate independently of column visibility; showing or hiding columns does not affect applied filters.
{% endhint %}
***
### Keyword Filter
Enter a word or phrase in the **Keyword Filter** above the list to find matching items.
* Searches are **not case-sensitive** and support **partial matches** (for example, `task` finds both `Task A` and `My Task`).
* The list updates automatically as you type.
{% hint style="info" %}
The **Keyword Filter** always searches the current hierarchy level and all nested levels, regardless of the selected **Hierarchy Level** setting. This allows you to find matching items in lower levels without changing the current view.
{% endhint %}
{% hint style="warning" %}
Keyword filtering is available only for columns indexed in **Elasticsearch**. The system verifies index availability before enabling the filter.
{% endhint %}
***
### All Filters
To access all available filters, select **All Filters** on the toolbar. This opens the **Filters Panel**.
You can filter by:
* **Default** (standard fields available as table columns)
* **Custom attributes** (user-defined fields specific to the items you're viewing)
{% hint style="info" %}
Filters applied through the **Filters Panel** also appear as chips in the **Quick Filters** area, including filters that do not normally appear there. This makes it easy to see and remove active filters.
{% endhint %}
***
## How Filters Work
Filters behave the same way whether you access them through **Quick Filters** or **All Filters**.
### Defining Filter Criteria
When you select a filter, a panel opens where you can specify the filter criteria.
Depending on the attribute type, you can:
* Select one or more values.
* Enter a word or phrase.
* Select a specific date or date range.
{% hint style="info" %}
#### Additional Options
Depending on the filter, the panel may also include:
* **Filter Operator** — Controls how the filter is evaluated.
* **Contains:** Returns items where the attribute contains the specified value.
* **Empty:** Returns items where the attribute has no value.
* **Not Empty:** Returns items where the attribute has a value.
* **Search Box** — Searches the available filter options.
* **Reset** — Clears the current filter criteria.
{% endhint %}
***
### Combining Filters
If a filter supports multiple values, selecting more than one value uses **OR** logic.
* For example, filtering **Status** by **In Progress** and **Published** returns items with either status.
Filters applied to different attributes are combined using **AND** logic.
* For example, applying **Status = In Progress** and **Priority = High** returns only items that meet both criteria.
***
---
# 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://interfacing.gitbook.io/interfacing-help-files/end-users/list-view-management/searching-and-filtering-in-list-view.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.
