> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/~/revisions/4ycMT0EcUe4aYSGLpT5Z/views/filter-fields.md).

# Filter fields

{% embed url="<https://www.youtube.com/watch?v=nq6eXGyzXio>" %}

In this video, learn how to:

* Add filter fields
* Test filters on views as the end user
* Customise single-option, number and related table filter fields
* Set default values
* Set conditional logic for when a filter field is visible
* Choose between 'Equal to' and 'Between' filter operators for number fields
* Filter records that show in filters for relationship fields
* Add a 'Search box' to enable users to search for values across all fields

### Overview

You can enable in-app filtering for your users so they can more easily find specific records. This is particularly useful for long lists of items.

In the example below, we enable filter fields based on the `Neighbourhood`, `Property Name` and `Status` fields which allows users to find properties that meet certain criteria much faster.

![](/files/fJjpG72MlKIki38460XO)

To access this feature, enter into edit mode (cmd + e) and head to 'Filter fields' section of the view. Then simply toggle on the fields you want your Users to be able to filter by.

<figure><img src="/files/wdliumo3JCfjf1yhmblu" alt=""><figcaption></figcaption></figure>

#### Search box

You can also add a *"Search box"* to any view that will search across any of your text/number fields that you have setup on the view instead of having to add multiple filters for each field.

<figure><img src="/files/ziCowSRJfRTYk8csFegQ" alt=""><figcaption></figcaption></figure>


---

# 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://guides.noloco.io/~/revisions/4ycMT0EcUe4aYSGLpT5Z/views/filter-fields.md?ask=<question>&goal=<endgoal>
```

`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.