> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/features/tableau-extension/configuration/schemas/general-features/conditional-visibility.md).

# Conditional visibility

Dynamically show/hide fields based on user responses

**Conditional visibility** lets you dynamically **show or hide form fields** based on a user’s input. This makes your forms smarter, cleaner, and more intuitive by only displaying relevant fields when needed.

### Available conditional operators

| Operator       | Description                                                                               |
| -------------- | ----------------------------------------------------------------------------------------- |
| `=`            | Checks if the field **is equal to** the specified value.                                  |
| `>`            | Checks if the field **is greater than** the specified value.                              |
| `<`            | Checks if the field **is less than** the specified value.                                 |
| `>=`           | Checks if the field **is greater than or equal to** the specified value.                  |
| `<=`           | Checks if the field **is less than or equal to** the specified value.                     |
| `!=`           | Checks if the field **is not equal to** the specified value.                              |
| `Contains`     | Checks if the field **includes** the specified text or value. Useful for partial matches. |
| `Not Contains` | Checks if the field **does not include** the specified text or value.                     |

#### **Examples**

You can use conditional visibility to make your form responsive to user choices.\
For example:

* **Show a comment box** only when the field `Status = Rejected`.
* **Display delivery details** only when `DeliveryMethod Contains "Courier"`.
* **Hide additional settings** when `EnableAdvancedOptions != true`.

***Note:** Conditional visibility only evaluates **actual values** present in the field.*

#### Scenarios:

In the example below, the field will only be displayed **if the user’s role is “C-level.”**

* **Controlling Field**: `role`
* **Operator**: `=` (equals)
* **Value**: `c-level`

As a result, the hidden field becomes visible **only when the user selects “C-level”** from the role dropdown

<figure><img src="https://content.gitbook.com/content/0gkOLIfzuEyMP2kvoT9o/blobs/SCXnMVaCGI3YFlEiRF2r/image.png" alt="" width="375"><figcaption></figcaption></figure>

#### How to Configure

1. Open the **Form Builder** in the schema configuration
2. Select the field you want to conditionally display
3. Under **Visibility Rules**, define the conditions (e.g., "Show if Reason = Other")
4. Save and publish

> ⚠️ Fields that are conditionally hidden will not be submitted unless shown and filled.

<figure><img src="https://content.gitbook.com/content/0gkOLIfzuEyMP2kvoT9o/blobs/qADpcaQCyt5DCan8ZYmA/Schermopname%202025-07-15%20om%2014.18.45%20(3)%20(1).gif" alt=""><figcaption></figcaption></figure>

#### Tips

* Use conditional visibility to reduce overwhelm in large forms
* Combine with **validation** and **masking** to ensure quality inputs only appear when needed
* Keep logic simple and test thoroughly for edge cases

> ⚙️ Conditional visibility works seamlessly with **Zapier** and other automation platforms. You can trigger workflows or notifications only when certain conditions are met in the form submission.


---

# 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.infotopics.com/writebackextreme/features/tableau-extension/configuration/schemas/general-features/conditional-visibility.md?ask=<question>&goal=<user_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.