> ## Documentation Index
> Fetch the complete documentation index at: https://filla.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Conditional visibility

> Show or hide individual fields based on answers the respondent has already given.

## What this does

Conditional visibility (also called show/hide rules) lets you show a field only when specific conditions are met. The field is completely hidden from the respondent until the conditions are true. It does not gray out; it disappears.

This keeps forms focused: respondents only see questions that are relevant to them.

## Setting up show/hide rules

<Steps>
  <Step title="Click the field">
    Click the field in the canvas to open its settings panel.
  </Step>

  <Step title="Open the Visibility rule">
    Expand the **Conditional visibility** section in the settings panel and click the **Visibility rule** trigger to open the rules dialog.
  </Step>

  <Step title="Add a condition">
    In the dialog, add a rule. Select the field to check, choose an operator, and enter a value. Click **Done** when finished.
  </Step>

  <Step title="Add more conditions (optional)">
    Add multiple conditions and set them to AND (all must be true) or OR (any must suffice).
  </Step>
</Steps>

## Supported operators by field type

| Field type                 | Available operators                                                                              |
| -------------------------- | ------------------------------------------------------------------------------------------------ |
| **Text**                   | contains, does not contain, is, is not, starts with, ends with, is empty, is not empty           |
| **Number**                 | greater than, greater than or equal, less than, less than or equal, between, not between         |
| **Date**                   | is on, is not on, is before, is after, is on or before, is on or after, is within, is not within |
| **Single/Multiple select** | has any of, has all of, has none of                                                              |
| **Checkbox**               | is checked, is unchecked                                                                         |
| **Any field**              | is empty, is not empty                                                                           |

## AND vs OR logic

When you have multiple conditions, you choose how they combine:

* **AND**: all conditions must be true for the field to show
* **OR**: any one condition being true is enough to show the field

You can also nest condition groups for more complex logic.

### Group negation

Each condition group can be negated. Instead of "All of" or "Any of", select "None of" to flip the group's logic. The group evaluates to true only when none of its conditions match. See [Building filter rules](/docs/logic/building-filter-rules) for details.

### Relative dates in conditions

When building conditions against date fields, you can use relative date values like "today", "this week", "last month", rolling periods (e.g., "in the last 7 days"), and ranges between two relative offsets. See [Building filter rules](/docs/logic/building-filter-rules) for the full list of relative date options.

## Example: Show a field based on a selection

You have a "Shipping method" select field with options "Standard" and "Express". You want to show a "Delivery instructions" text field only for Express orders.

On the "Delivery instructions" field:

1. Add a visibility rule
2. Condition: `Shipping method` `has any of` `Express`

The field appears immediately when the respondent selects Express, and disappears if they change to Standard.

## Hidden fields and submission

A hidden field is not validated and not submitted. If a field is required but hidden (because its conditions aren't met), the required check is skipped. Only the visible fields are included in the submission.

<Warning>
  If a field has a value from a previous interaction and then becomes hidden, its value is cleared before submission. The respondent's hidden answer is not saved to Airtable.
</Warning>

## Common questions

<AccordionGroup>
  <Accordion title="Can I base a condition on a field from a previous page?">
    Yes. Any field already in the form, including fields from earlier pages, can be used in show/hide conditions.
  </Accordion>

  <Accordion title="Can I hide a whole section, not just a field?">
    Yes. Sections (the grouping widget) also have show/hide rules. Hiding a section hides all the fields inside it at once.
  </Accordion>

  <Accordion title="Can I show a page based on conditions?">
    Page-level visibility is a separate feature. See [Page visibility](/docs/logic/page-visibility).
  </Accordion>

  <Accordion title="What if the condition references a field that hasn't been filled yet?">
    An empty field evaluates to "empty" in conditions. If your condition is "is not empty", it won't trigger until the respondent fills in that referenced field.
  </Accordion>
</AccordionGroup>