> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/use/views/filtering-system.md).
# Filtering System
The filtering system lets you narrow down the submissions displayed in any view. You can combine multiple filters to refine your results.
Filter options depend on the field type:
* **Number:** Empty, Not empty, Equal to, Greater than or equal to, Less than or equal to, Between
* **Date:** Year, Month, Week, Day, Between
* **Text:** Empty, Not empty, Contains, Does not contain, Equal to, Starts with, Ends with
* **Image:** Exists, Does not exist
* **List:** One or more options are selected
Filters stack: a submission must match **every** active filter to appear. For example, filtering by Status = "In progress" **and** Technician = "Alice" shows only Alice's in-progress submissions.
Active filters are remembered until you reset them.
## Viewing active filters
Every active filter also appears as a removable chip on the top bar of the view, so you always know what's being filtered without opening the filter pane. This is particularly handy when taking screenshots to share or document, screensharing during a call, or opening a shortcut and not remembering which filters it applies.
* Click the **X** on a chip to remove that filter instantly, without opening the pane.
* Inside the filter pane itself, the filtered value of each field is now shown directly, so you can review your filters without expanding every field's settings.
{% hint style="info" %}
Available on **Web**, across all views (table, gallery, mixed, map, and calendar).
{% endhint %}
## Managing available filters
By default, all fields and metadata of a form appear in the filter pane. Only admins can configure which fields are available as filters and in what order — so that the filter pane only shows what is relevant to users.
{% hint style="warning" %}
This configuration applies to **all users** and **all views** of the form (table, gallery, mixed, map, and calendar). Any change you make here affects everyone immediately.
{% endhint %}
### Opening configuration mode
1. Open any view on the form you want to configure.
2. Open the filter pane.
3. Click the **Configure filters** icon at the top right of the pane.
The pane switches to configuration mode, listing all available fields and metadata.
### Selecting filterable fields
* **Check** a field to make it available as a filter.
* **Uncheck** a field to hide it from the filter pane.
### Reordering filters
Drag and drop fields to define the order in which they appear in the filter pane.
### Applying and resetting
* Click **Apply** to save the configuration. Only the selected fields appear as filters, in the order you defined, for all users on all views of this form.
* Click **Reset** to revert to the default behaviour: all fields visible, in form order.
### Limitations
{% hint style="info" %}
The configuration is **per form**, not per view or per user — one setup applies to all views of the form for every user.
{% endhint %}
If a field is removed from the form after being configured as filterable, it is automatically and silently removed from the filter configuration.
---
# 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://www.center.daxium-air.com/user-documentation/use/views/filtering-system.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.