> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/dynamic-components/components/checkbox.md).

# Checkbox

The Avonni Checkbox component lets admins embed a boolean toggle in any page. Use it when you need users to confirm a choice, accept a condition, or set a true/false value as part of a flow.

## Overview

The Checkbox renders a single labelled checkbox input. It supports required validation, a disabled state, and four label-display variants so it fits naturally alongside other form fields.

## Configuration

To configure the Checkbox, select it on the canvas. The **Edit Checkbox** panel opens on the right. The sections below mirror the configuration panel from top to bottom.

### Properties

#### Label

The text that identifies the checkbox to the user. Accepts a static value or a dynamic expression mapped to a Salesforce field.

#### Checked

Controls whether the checkbox is selected by default. Enable this toggle to pre-check the box when the component loads.

#### Field Level Help

Help text displayed as a tooltip next to the label. Use it to detail the purpose and function of the checkbox so users understand what they are confirming.

#### Variant

Changes how the label is positioned relative to the checkbox.

| Value                  | Description                                                              |
| ---------------------- | ------------------------------------------------------------------------ |
| **Standard** (default) | Label appears above the checkbox.                                        |
| **Label Hidden**       | Label is not visible; useful when the context makes the purpose obvious. |
| **Label Inline**       | Label appears to the right of the checkbox on the same line.             |
| **Label Stacked**      | Label is stacked above the checkbox in a compact form layout.            |

#### Required

When enabled, the user must check the box before the form can be submitted.

#### Message When Value Missing

The error message displayed when the checkbox is left unchecked and the form is submitted. Requires: **Required** = enabled.

#### Disabled

When enabled, the checkbox is read-only and users cannot interact with it.

#### Message When Bad Input

The error message displayed when the component detects an invalid input state. Available under advanced options.

### Set Component Visibility

All components support conditional visibility — see [Component Visibility](/dynamic-components/core-concepts/component-visibility.md).

## Interactions

[Interactions](/dynamic-components/component-builder/interactions.md) define what happens when users interact with the Checkbox. Configure them from the **Interactions** tab of the Edit Checkbox panel.

### Change

Fires when the user checks or unchecks the box. Use this interaction to trigger downstream logic — for example, showing or hiding other components, updating a variable, or advancing a flow.


---

# 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://docs.avonnicomponents.com/dynamic-components/components/checkbox.md?ask=<question>&goal=<endgoal>
```

`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.