Switch fields store one true-or-false value. Runtime users turn the switch on or off.
Use a switch field when the value is a binary state, such as completed, enabled, confirmed, reviewed, or accepted.
Basic Settings
| Setting | Description |
|---|
| Name | The field label shown to users. It is required and should describe the binary state clearly |
| API Name | The stable technical name used by data APIs, scripts, formulas, imports, and integrations. It is required |
| Required | Requires the field to have a value before the record can be saved |
| Readonly | Shows the value but prevents users from changing it |
| Disabled | Makes the field unavailable for normal use |
| Hidden | Stores the value while hiding it from normal form pages |
Switch Field Config
| Setting | Description |
|---|
| Checked Label | Text shown for the enabled state |
| Unchecked Label | Text shown for the disabled state |
| Must Be True | Requires the switch to be enabled before the record can be saved |
| Must Be True Message | Custom message shown when the switch must be enabled but is not |
| Validate Trigger | Controls when validation runs: when the value changes, when the field loses focus, or when the record is submitted |
| Field Color | Sets the display color used for the field |
| Help Text | Helper copy shown near the field. Use it to explain what enabling the switch means |
Common Examples
| Scenario | Checked Label | Unchecked Label |
|---|
| Task completion | Completed | Not Completed |
| Review state | Reviewed | Not Reviewed |
| Agreement | Accepted | Not Accepted |
| Feature state | Enabled | Disabled |
Configuration Tips
| Tip | Description |
|---|
| Name the positive state | A name such as Completed or Confirmed makes the checked state obvious |
| Use must-be-true for confirmations | Turn it on when users must explicitly accept or confirm something |
| Keep labels short | Short labels are easier to read beside a switch |