Show and hide questions with conditional logic

Ask follow-up questions only when they are relevant, skip whole steps, or disqualify an answer.

Who can do thisowneradmin

Logic keeps a form short by asking each person only what applies to them. "Do you need parking?" then, only if yes, "What is your registration plate?"

How a rule is built

Every rule is: when these conditions match, do this.

Open a field's settings in 4 Form fields and find its logic section.
Field logic panel with match all or any, a condition row and an action
Choose whether to match ALL conditions or ANY of them.
Add conditions. Each is a field, an operator and a value.
Choose the action.
Save.

The operators

Operator	Matches when the answer
equals	is exactly this value
≠	is anything other than this value
contains	includes this text
not contains	does not include this text
is empty	was left blank
is not empty	was answered
>	is greater than this number
<	is less than this number
is one of	matches any value in your list
not one of	matches none of the values in your list

The actions

Show — the field is hidden until the conditions match. The most common one.

Hide — the field is visible until the conditions match, then disappears.

Make required — visible either way, but only compulsory when the conditions match. Use this for "if you selected a workshop, tell us which".

Make optional — normally required, relaxed when the conditions match.

Skip step — jumps a whole step. Good for skipping "Travel and accommodation" for local attendees.

Disqualify — ends the registration. Use it for a genuine eligibility gate, such as an under-18 answer on an adults-only event.

Disqualify stops someone registering, and the wording they see should explain why. Test it yourself before publishing — an accidental disqualify rule silently turns away real registrants and produces no error you would notice.

Keep it simple

Logic is easy to over-build. A few habits that hold up:

Prefer Show over Hide. Reads more naturally and is easier to test.
Base conditions on Dropdown and Radio answers, not free text. "contains" on a text field depends on spelling.
Do not chain rules more than one level deep.
Test as each attendee type, answering each branch.

Common problems

A field never appears. Its conditions cannot all be true at once — usually ALL where you meant ANY.

A field always appears. The condition references a field on a *later* step, so it has no answer yet. Conditions must depend on earlier answers.

A required hidden field blocks submission. Required and hidden together is a dead end. Use Make required in the rule instead of leaving it permanently required.

Skip step skips too much. A skipped step's fields are not answered at all — check nothing compulsory lives there.

It behaves differently on the live form than in preview. Preview shows the current draft. Save and publish, then test the real form.