Sections, columns and repeating groups
The Layout group in the palette holds three blocks that shape a page rather than ask a question. Each one wraps the fields you put inside it.
Sections
Section titled “Sections”A Section groups fields under a heading. It is a real group, not a visual divider: a visibility rule on a section hides everything inside it, and the fields within one are wrapped in a bordered group with the heading on top, styled from your theme.
A section can also be collapsible. Select the section marker and, in Section settings, tick:
- Collapsible: respondents can fold and unfold the section.
- Start collapsed: it arrives closed. This option appears only once Collapsible is ticked.
Give the section a label before making it collapsible. The show and hide control takes its name from the label, so an unlabelled collapsible section leaves anyone using a screen reader with a button their software cannot announce. The builder asks you for a label first.
Collapsing is presentation, never visibility. A collapsed section’s fields still count: answers stay in the submission, rules still evaluate, and a required field inside a collapsed section still blocks submit. If you want a section to genuinely disappear for some respondents, give it a visibility rule instead.
Columns
Section titled “Columns”A Columns block lays fields out side by side, with a Column Break separating one column from the next and an End Row marker closing the block. Fields inside a columns row whose rule is false are dimmed on the canvas, matching what respondents see.
Repeating groups
Section titled “Repeating groups”A Repeating Group collects a set of answers more than once: line items, attendees, assets, addresses. Respondents add and remove rows, and each row creates a child record against the object you mapped its fields to.
Repeating groups render everything you can put inside one, including columns, description text, and hidden values in every row. They can also be nested: inner rows create their child records under the right parent, so a form can capture, for example, sites and then the assets at each site.