Combined onboarding card for creating a workspace with name and URL slug, plus a team invite section with email inputs. Perfect for SaaS apps that require team collaboration setup.
Single-screen setup card that combines workspace name/URL fields with a dynamic list of teammate email invites. The email rows are the only genuinely interactive part of the block: workspace name and URL are plain uncontrolled inputs whose values are never read.
Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.
Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.
Radix flavor
npx shadcn add "https://ui.beste.co/r/onboarding14?email=YOUR_EMAIL&license_key=YOUR_KEY"Base UI flavor
npx shadcn add "https://ui.beste.co/r-base/onboarding14?email=YOUR_EMAIL&license_key=YOUR_KEY"This installs the block to components/beste/block/onboarding14.tsx and the badge, button, input, and input-group shadcn/ui primitives it depends on.
The installed file exports onboarding14Demo alongside the block: the exact props behind the preview above. Spread it to get a working workspace setup card in one line.
import { Onboarding14, onboarding14Demo } from "@/components/beste/block/onboarding14";
export default function OnboardingPage() {
return <Onboarding14 {...onboarding14Demo} />;
}Then replace the demo with your own props. Written out, a trimmed setup looks like this:
import { Onboarding14 } from "@/components/beste/block/onboarding14";
export default function OnboardingPage() {
return (
<Onboarding14
badge={{ label: "Workspace", variant: "secondary" }}
heading="Create your workspace"
description="Set up a home for your team. You can change this later."
primaryButton={{ label: "Create & Continue", href: "/dashboard" }}
secondaryButton={{ label: "Skip for now", href: "/dashboard" }}
labels={{
workspaceName: "Workspace name",
workspaceUrl: "Workspace URL",
urlPrefix: "app.example.com/",
}}
currentStep={2}
totalSteps={3}
/>
);
}| Prop | Type | Default | Description |
|---|---|---|---|
badge | { label: string; variant?: "default" | "secondary" | "outline" } | – | Small badge above the heading |
heading | string | – | Main headline |
description | string | – | Supporting copy below the heading |
primaryButton | { label: string; href: string } | – | Primary CTA below the card |
secondaryButton | { label: string; href: string } | – | Secondary/outline CTA next to the primary one |
labels | Labels | – | Text overrides for every field label, placeholder, and section heading in the card |
currentStep | number | 1 | Display-only step number used in the step label |
totalSteps | number | 4 | Display-only total step count used in the step label |
className | string | – | Extra classes for the outer <section> |
type Labels = {
stepOf?: string;
workspaceName?: string;
workspaceNamePlaceholder?: string;
workspaceUrl?: string;
workspaceUrlPlaceholder?: string;
urlPrefix?: string;
inviteHeading?: string;
inviteDescription?: string;
emailPlaceholder?: string;
addAnother?: string;
};emails is real useState<string[]> seeded with one empty string, with addEmail/removeEmail/updateEmail handlers behind the "Add another" button and each row's remove icon. The remove button only appears once there is more than one row.Input/InputGroupInput elements with no value or onChange, so whatever the user types there is never read by the component or exposed through any prop or callback.labels?.field ?? "...", not via a merge with the demo module's own labels object the way onboarding1's labels work.currentStep/totalSteps only feed the "Step of " text above the card (the same .replace("{current}", ...)/.replace("{total}", ...) pattern used in onboarding13); there is no internal step state, so this block renders a single fixed screen rather than advancing through multiple screens.InputGroup/InputGroupAddon/InputGroupText to render a fixed prefix (app.example.com/ by default) inline with the input, rather than a plain label above a bare Input.primaryButton and secondaryButton are plain links, so wiring up the actual "create workspace" request is left entirely to the consuming page.Wiring the form up
This block ships the form markup only; state, validation, and submit are yours to add. Our guide wires the shadcn Field primitives to React Hook Form, TanStack Form, and Formisch on one field system.
onboarding19
Onboarding screen with a form card for setting up user profile including avatar, display name, bio, and timezone. Perfect for the personal details step in any SaaS onboarding flow.
onboarding29
Onboarding screen for collecting company information including name, team size selector chips, and industry dropdown. Perfect for B2B SaaS apps that need organizational context during setup.
onboarding23
Onboarding screen for configuring account security including two-factor authentication, recovery email, and backup codes. Perfect for apps that prioritize security during onboarding.
onboarding15
Onboarding screen with a grid of available integrations showing connection status and connect/skip actions. Perfect for apps that rely on third-party services like Slack, GitHub, and Google.
onboarding20
Onboarding screen with a grid of starter templates to choose from, each with a preview thumbnail, title, and description. Perfect for project creation flows in design tools and project management apps.
onboarding26
Onboarding screen with import options from other platforms, CSV upload, and manual entry. Perfect for SaaS migration flows that help users bring existing data into the platform.