Yes/No

The Yes/No field is a simple toggle that stores a Yes or No value. It's the right choice for any data that has exactly two states - on or off, true or false, accepted or not.

What it is

A Yes/No field displays as a toggle switch. Users flip it on for Yes or off for No. No typing, no dropdowns - just a single clear binary choice. You can configure it to default to Yes so users don't have to touch it for the most common answer.

When to use it

Active/inactive status - mark whether a record is currently active or has been deactivated
Opt-in flags - track whether a contact has opted in to marketing emails or SMS
Approval checkboxes - record whether something has been reviewed and approved
Terms & Conditions acceptance - require users to confirm they've agreed before saving
Feature flags - track whether a feature or option is enabled for a specific record
Completion status - mark a task or checklist item as done

Using Yes/No as a required agreement: If you mark a Yes/No field as Required , the record cannot be saved unless the field is toggled to Yes . This makes it perfect for Terms & Conditions - your team or customers must actively confirm before a record is created.

Settings

Label - the name shown above the field in forms and layouts
Enabled by Default - when turned on, the field starts toggled to Yes on new records; useful when Yes is the most common answer
Required - when enabled, the record cannot be saved unless the field is set to Yes
Conditional - show or hide the field based on another field's value

Example

In a client onboarding app, you add a Yes/No field labeled Agreed to Terms to your Clients object type. You mark it Required. When your team creates a new client record, the toggle starts at No by default. Before the record can be saved, the toggle must be switched to Yes - confirming the client has agreed to your terms of service. This gives you a clear, auditable record of acceptance stored directly on the client's profile.