Steps

In the app builder, add each form as a step and drag them into the order a respondent should work through. The order is the session; step two is not reachable as a separate page and does not need its own link.

Give each step a title and an optional icon. The title is what appears as the section heading during the session, so it can be friendlier than the form's own name.

A repeatable step takes a minimum and a maximum. A minimum of one means the session cannot be submitted without at least one entry; a maximum caps it. A mandatory repeatable step shows one empty entry to begin with — asking someone to press Add before they can start is a step people miss.

Mark a step optional and it can be left empty. Give it a conditionand it appears only when an earlier answer calls for it — a follow-up block that only applies when the first answer was “yes”.

A step that is hidden by its condition is not validated and not submitted. As with conditional logic on a form, nobody is blocked by something they were never shown.

With Allow drafts on, a session can be left and picked up later, which matters when a visit is interrupted or the connection is poor. With it off, a session must be completed in one sitting.

Periods are reporting windows — a quarter, a term, a campaign. When an app has periods configured and none is currently open, it tells visitors it is between cycles rather than accepting data against no period at all. Sessions are stamped with the period they were collected in, which is what makes quarter-on-quarter comparison possible later.

The Design → Layout setting applies to every step at once: stacked, or two-column on wide screens. It is app-wide deliberately — changing column count between step two and step three reads as a fault rather than a design. Both collapse to a single column on phones.