Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Onboarding Flow Settings Block for React

An onboarding flow editor with a funnel: five steps in order with a bar of who finishes each, switches to turn steps off, a Required toggle, Move up and Move down, the biggest drop worked out again after every change, and a drawn screen of the step people see.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Decide which first-run steps a new account sees, and see what each choice does to the people who get through, with this onboarding flow editor for React with Base UI. A hairline frame with a plus mark on each corner opens with a strip of three figures: how many of 1,000 new accounts finish, the step where the most people drop, and how many steps are on. Under it the steps run in order, each with a bar of how many finish it and a hatched stretch for those who drop there, a Switch that turns it on or off, a Toggle that makes it required, and Move up and Move down Buttons. Turning a step off removes its drop and works out everything after it again; moving a step changes where people drop and says the new place. Choosing a step draws the screen people see for it beside the list, with a Skip for now link only when it isn't required. The action foot counts unsaved changes beside a Shine Button to save and an outline Button to discard. On a phone each step is a card and the drawn screen sits under the list. It's built from Switch, Toggle, Button, Shine Button and Guides, with the bars drawn in CSS and a CSS entrance only. For an activation tool, a product tour builder or any app whose sign-up has more than one step.

FAQ

Where do the numbers come from?

They are typed example figures, not measurements: STARTERS is the 1,000 new accounts and each step in SAVED has a keep, how many of every 1,000 people who reach it finish it. A step's count is the count before it times its rate, so the bars and the strip are always worked out from the same list, and the line under each figure is built from the same numbers. Replace keep with rates from your own analytics, or compute the counts on your server and pass them in.

What happens to the figures when a step is turned off?

Everyone who reaches it goes straight on to the next one, so it has no drop, its bar is left empty and its count reads Off. Every later count is worked out from the step before it that is still on. The first step, creating the account, is always on and always required, and nothing can be moved above it.

Does the order change the result?

It changes where people drop, not how many make it to the end: the rates are multiplied, so the last figure stays the same, while the bars, the biggest drop and the strip's second figure move. Move up and Move down are buttons named for their step ("Move Invite teammates up"); the one that can't act stays focusable and says why in the status line, and after a move focus stays on the button you pressed. There is no drag handle.

What does Required do?

A required step has no Skip for now in the drawn screen, and the strip counts how many steps are required. It doesn't change the figures: the demo has no skipping rate, so a required and an optional step with the same rate count the same. If you measure skips, make them part of keep.

What stays local, and how do I wire it up?

Everything. Save keeps the edited steps as the saved ones, in this page only, and Discard puts the saved steps back; the status line counts how many settings differ. To make it real, send the saved list (each step's id, whether it is on, whether it is required and its position) to your API in the save handler, and build your onboarding from the same list. Save and Discard stay in place and focusable while nothing changed, and answer "No changes to save." in words.

Is it accessible, and how does it look on a phone?

Each step is a radio in one group, named by the step and described by its hint, so the arrow keys move the preview between steps; the switch, the toggle and both move buttons are named for their step. The bars are decorative and the same facts are text beside them ("540" and "372 drop here"). The drawn screen is hidden from assistive technology and its caption says the same in words. Below the medium breakpoint the list is a stack of cards and the drawn screen follows it; the save bar stays pinned to the bottom of the screen.

  • Pro

    A contract tool's get-started guide as a setup panel: six steps in a single-open accordion with one button in the open step, a count that follows what you finish, a menu that hides completed steps or the guide, and a pill that opens it again.

  • Pro

    Setup Wizard Onboarding

    Profile and account

    A team workspace's first-run wizard as a whole screen: a rail of four steps (account, workspace, invites) that ends on a recap of every answer with an Edit button per section, and a Continue that checks each step first.

  • Pro

    Default Values Settings

    Fields and forms

    A task defaults panel: a priority, an assignee, days until due (calendar or working days), an estimate, up to four labels and who can see a task, beside a drawn new task that shows every default applied and the due date worked out from a fixed day.

  • Pro

    A sign-up form editor where the form is the editor: a drawn sign-up page with six fields, each with a Required toggle, a Show switch and Move up and Move down, a locked email and password, and a Publish form button in a slim bar.

  • Pro

    Custom Fields Settings

    Fields and forms

    An Add field sheet open over a drawn Contacts table: a name, a type picked from six cards, the options that belong to that type, a live preview of the field, and an Add that appends a column to the table behind it.

  • Pro

    User Fields Settings

    Fields and forms

    A profile fields panel: a table with a row per field showing its type, a Required switch, who can see it and its rule in words, with rules that open in place (a preset, the shortest and longest answer and a Try a value field that says Valid or why not) and the member's form drawn from the same fields.