boolean_toggle

A checkbox records a choice; a switch does something. That is the design language this widget buys you, and Odoo backs the look with matching behavior: the source extends the standard boolean field and overrides one method, onChange, which updates the value and, when autosave is on, saves the record in the same breath.

Autosave is the default, verified in extractProps: unless the option is explicitly false, every flip is a commit. In a list view that means toggling ten rows is ten saved records with no Save button involved, which is exactly why core uses it for active flags and configuration tables.

Use the toggle where flipping is the action: activating a carrier, publishing a product, enabling a rule. Users get the instant-effect behavior the switch shape promises, and admin screens stop needing save-button choreography.

The same instantness is the caution. Because the save commits the whole record, a toggle on a form quietly persists every other half-typed edit on it, and automations watching the record fire immediately. On records where edits are usually deliberate and batched, quotations, invoices, anything with validation, either set autosave: False or stay with the plain checkbox, and keep the switch for genuinely switch-like flags.

Our rule on implementations: toggles in lists and settings pages, checkboxes inside documents.

Studio applies this widget without code.

1. Open the view in Studio and select the boolean field.

2. In Properties, set Widget to Toggle. The Autosave checkbox Studio shows corresponds to the option below.

Nothing meaningful is XML-only for this widget; the single option is exposed. What Studio cannot decide for you is the judgment call above, where instant saving is appropriate.

Active flag in a list

<field name="active" widget="boolean_toggle"/>

Each flip archives or restores that row immediately, no save step.

Toggle without instant saving

<field name="is_published"
       widget="boolean_toggle"
       options="{'autosave': False}"/>

The switch look with checkbox semantics: the change rides along with the normal record save.

Read-only under a condition

<field name="is_locked"
       widget="boolean_toggle"
       readonly="state != 'draft'"/>

Standard readonly expressions apply unchanged, inherited from the boolean base.

Because a flip can be a save, everything downstream of a save happens per flip, and that is worth spelling out once.

Automations and computed fields run immediately. An automated action on the field, or on the record's write, fires at the click. Ten toggles in a list are ten separate writes, ten automation runs, ten log entries.

Access errors surface at the click. With a checkbox, a user without write rights finds out at save time; with an autosave toggle, the click itself errors. Same rule, earlier feedback.

Concurrent edits get interesting. If another user changed the record since it loaded, the flip's save meets Odoo's standard concurrency handling right away rather than at a later save. Rare, but support tickets about "the toggle refused" are usually this.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The changes below are read from the public development branch and are not final until release.

Nothing changes for this widget. Same single autosave option, same true default, same record-save semantics. Internal syntax moves to the new Owl props system, affecting JavaScript patches only. We re-verify once Odoo 20 ships.