> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/data/collections/field-types/boolean.md). # Boolean (Yes/No) Fields Boolean fields hold True/False or Yes/No values and are excellent for indicating the status of a task. In forms, they can be displayed as a checkbox or a dropdown of Yes / No. ## Display Options * **Checkbox** The field appears as a checkable box that users can click to toggle between true and false * **Dropdown** The field appears as a dropdown menu with "Yes" and "No" options ## Use Cases Boolean fields are perfect for: * Task completion status (Done/Not Done) * Feature toggles (Enabled/Disabled) * Approval workflows (Approved/Pending) * Subscription status (Active/Inactive) * Availability indicators (Available/Unavailable) * Permission flags (Public/Private) ## Best Practices * Use clear, descriptive field names that indicate what "true" means (e.g., "Is Active" rather than just "Status") * Consider the default value - should new records start as true or false? * Use checkboxes for quick toggling, dropdowns when you want to be more explicit about the choice * Boolean fields work great in filters and conditional logic for workflows --- # 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://guides.noloco.io/data/collections/field-types/boolean.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.