> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/yes-no-boolean.md).

# Yes/no (Boolean)

Store a simple yes-or-no state such as approved, active, or complete.

Use a **Yes/no** field for simple yes-or-no states such as approved, active, or complete.

For the general settings all data fields have in common, see [Shared field settings](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/shared-field-settings.md).

Field-specific settings for **Yes/no** or **Boolean** are:

#### Everywhere

* **Default value**: preselects the initial yes-or-no state for new records

#### On the form

**Display**

* **Display as**: shows the options as **Checkbox**, **Dropdown**, **Switch**, or **Tabs**

We recommend using **Default value** to make filters and conditions easier to handle in automations. A default value ensures new records start as either "yes" or "no", instead of remaining empty.\
Without a default value, the field can have three states: "yes", "no", or "empty".\
For example, if you filter for `field_value = false`, records with an empty value are not included, even though users may treat them as no.


---

# 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.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/yes-no-boolean.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.