Skip to main content

​
Required steps

Use Required steps when a signed-in role must finish something before they can use the rest of the portal. Typical cases: first login intake, a waiver, an annual acknowledgment, or a short onboarding sequence. This is not public intake. Guests who never sign in still use a published form link. Required steps run after login, after the End-User Platform Terms, and after any app privacy notice. Owner and admin accounts skip required steps. Preview as a customer role to see the gate.

​
What builders configure

Ask Building chat to set required steps. You choose:
  • Which roles must complete them
  • An ordered list of forms and/or pages
  • Whether the rest of the app stays locked, or only some pages, tools, or chat
  • Optional renewal after a number of days
  • Optional adoption when a data field already shows the person finished
App Settings → Access shows a read-only list of journeys, roles, steps, and lock mode. Change them in Building chat. End users see the published set. Preview Draft and Building chat use the live draft.

​
What the person sees

After they accept platform terms and any privacy notice, the portal opens the current step. When the journey locks the whole app, a form is a full page (not a dismissible popup) and a page step hides other navigation. When only some pages, tools, or chat are locked, the rest of the portal stays open and a banner at the top lets them continue the form or page. Submitting the current required form, or finishing the page step, unlocks the next step or the rest of the app. Submitting a different form does not skip the current step. A later step can depend on an answer from an earlier form in the same journey.