Show fields with conditional logic

Set a condition

1. Open Dashboard, choose Selling, and find the form in My Forms. Choose Edit form (the labeled icon in List view).
2. In the Builder, choose Build, then select the field that should appear or disappear on the form canvas.
3. In its Properties panel, scroll to the Conditional Logic section. On a phone, selecting the field opens the Properties drawer; the condition controls are inside that drawer. If a text block opens an inline toolbar instead, choose Properties on that toolbar.
4. Choose Add condition.
5. Select the source field whose answer controls visibility, then choose an operator and the comparison value.
6. Preview every branch, then choose Save changes to publish the valid rules. On a shared form, your role must allow editing its fields.

Only an earlier supported field can be a source. Put the controlling question before the dependent block. If a source is deleted or moved after its dependent block, the builder marks the rule invalid: autosave may protect the incomplete draft, but Save changes blocks publication until you use an earlier source or remove the invalid rule.

With no earlier supported source, the section says Add earlier fields first to create conditions instead of showing Add condition. Form Header, Payment Instructions, Page Break, Divider, Heading, and Hyperlink blocks do not offer a Conditional Logic section.

Text choices support equals, does not equal, contains, does not contain, starts with, ends with, is empty, and is not empty. Number, Currency, Rating, Slider, and Calculation sources also support greater than, less than, at least, and at most. Date and Time use the equivalent after, before, on or after, and on or before comparisons.

Combine conditions

Choose ALL when every rule must match or ANY when one matching rule is enough. Keep the smallest rule set that expresses the buyer journey; overlapping rules are harder to test and explain.

The comparison control follows the source type.

• Dropdown, Single Choice, Checkboxes, Image Choice, and Multiple Choice offer their saved options.
• Date and Time use their respective pickers; Rating offers one through five stars; Slider, Number, Currency, and Calculation use numeric input.
• A Payment Instructions source can match an exact displayed method or a broad saved method type such as any crypto method.
• Agreement uses Checked or Unchecked, while Coupon Code uses Applied or Not Applied.
• File Upload, Payment Proof, Hidden Field, Phone, and text-like sources can also be used where the available value and operator fit the workflow.

Test hidden required fields

A required field that is hidden by a condition is skipped during validation and does not block submission. Test both the visible and hidden state, including returning to an earlier page or answer after filling the dependent field.

Conditional visibility is a buyer-interface feature, not authorization. Hidden fields and content are still delivered to the buyer's browser. Never use a condition to protect secrets, private instructions, or access-controlled content.

If the source choice was renamed, reopen the rule and confirm that it still targets the intended value. See Choose sections and question fields for the supported field types.