> 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/build/building-forms/conditions.md).

# Conditions

Use conditions to dynamically show or hide fields based on user input.

## Introduction

Conditions can be used in:

* Field permissions
* [Automatic generation of reports](/user-documentation/build/building-the-reporting/report-types/automatic-reports.md)
* [File distribution](/user-documentation/build/building-forms/submission-broadcast.md)
* [Workflows](/user-documentation/build/building-forms/workflow-and-assignation.md)
* [Automation](/user-documentation/build/building-forms/automations.md)

{% hint style="info" %}
If you use the field of *current user* in a condition, it can only be used for permissions and workflows — it will not work in reports, automation and broadcasts. Conditions only work on the last active [version](/user-documentation/components-concepts-terminology.md#version) of the form.
{% endhint %}

## Field Permissions

A field can be:

* Visible
* Editable
* Required

This setting is done in the field permissions. The **YES** and **NO** values are available by default and to these values are added the conditions created.

A condition is a field (or list of fields) with an associated value.

For the condition to be satisfied, all field values must be checked on the field on which the condition was applied.

You can configure different combinations of conditions to allow fields to interact with each other based on one or more results. It is also possible to use another condition to create a new, more complex condition.

## Setting up

In your form, click **Condition**. The following window lists all the conditions of your model.

* Go to New:

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-effb8df116be62cf73fdd7050b2f9b4215b0c208%2Fdda3d7_1914016b25cf4e14a88a1523c1d80f69~mv2.png?alt=media)

We will address the following elements point by point:

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-9eaa339240d62b2c0740cc482100be8deafc5d25%2Fdda3d7_78e7882a2cd9415b8c51ff181bceae76~mv2.png?alt=media)

1. Name your condition to differentiate them.
2. List of all the fields in your Form.
3. The selected field (e g. Status - list field) and offers an operator and result value that you must choose.
4. **Possible values** returns all the data contained in your list field.
5. Combination elements are used to link the display based on different result criteria.
6. Result of your condition in color-coded JavaScript format.

* **Green** = Valid syntax.
* **Red** = Invalid syntax.

A condition is linked to the elements of your form, however if a change is applied such as a list change or a field deletion, then your conditions that depend on it will be invalidated. Modification or deletion of these is necessary in order to be able to save your form with the new modifications.

**Example:** In the following example, the condition matches two values from two different lists. During entry, as soon as the result is "**Status: Employee**", the condition displays the desired field. If the condition is valid, a confirmation message appears. If the result is **red**, the condition is not correctly written — you will not be able to save the form until it is fixed.

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-4f73e6062e9cefe35d1e42e52435199da62978fb%2Fdda3d7_574f19572547454ba4a3535da569c35a~mv2.png?alt=media)


---

# 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://www.center.daxium-air.com/user-documentation/build/building-forms/conditions.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.