FIELDS

Consent field

Configure an unchecked Consent checkbox in Logical Forms and record acceptance together with the wording shown for that submission.

2 min read · Updated November 19, 2026

Use Consent when a visitor should actively accept a statement. The field records acceptance and a snapshot of the displayed wording. It starts unchecked and has no prechecked-default setting.

Availability: Core (Free).

Add and configure the field

  1. Open the form in Build and add Consent from Add fields.
  2. Select its canvas card to open Field options, then configure the controls below.
  3. Save the form and check its saved Preview and embedded page.

Field-specific settings

Setting What it does
Checkbox label Checkbox label: the statement beside the checkbox. Basic links, emphasis, strong text and line breaks are supported.
Description Description: a Visual/Code editor for supporting wording. Permitted paragraphs, lists, headings and basic formatting render in a bordered block below the checkbox by default. The content limit is 64 KiB; scripts, media and general shortcodes are excluded.

Applicable shared options

This field also provides Label, Required, Description placement, Validation message placement, Required message, Invalid value message, CSS classes, Hide label, Admin label. See common field options for their behavior.

Answers and behavior

Required starts enabled. An optional Consent can be submitted unchecked. A required unchecked checkbox fails validation. Changing the ordinary Description or Validation message placement follows the shared form/field placement controls.

The entry stores accepted or not accepted together with the field label, checkbox wording and description from that capture. Changing the form's wording later does not replace existing snapshots. Editing an unrelated answer does not regenerate them either.

Entry details display the recorded agreement block. Ordinary merge tags and summaries show acceptance plus the saved checkbox wording; {field:5.description} returns the saved description as plain text when 5 is the field ID. CSV offers recorded wording columns. The snapshot does not archive the contents of a linked policy page or PDF.

Normal conditions can control whether Consent applies. Inactive Consent is omitted; an optional unchecked, applicable Consent records not accepted. Repeater rows can each have their own Consent snapshot.

Example and checks

Set a short checkbox statement such as I agree to the project terms, link the relevant page and explain the scope in Description. Save and test both checked and unchecked cases. Confirm the entry shows the wording used for that submission.

If you revise the wording, make a fresh test submission and compare the two entries. Keep the published policy itself under your own revision process when historical policy contents matter.

Use the testing checklist to check validation and the saved entry. Explore all fields provides live examples.