Workspace Setup with Team Invite

Step 3 of 4

Workspace

Create your workspace

Set up a home for your team. You can always change these settings later.

app.example.com/

Invite your team

Collaborate with your colleagues from day one

About this block

Workspace Setup with Team InvitePRO

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.

Onboarding14: Workspace Setup with Team Invite

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.

Upgrade to Pro

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.

Upgrade Now

Installation

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

bash
npx shadcn add "https://ui.beste.co/r/onboarding14?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

bash
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.

Quick start

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.

tsx
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:

tsx
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}
    />
  );
}

Props

PropTypeDefaultDescription
badge{ label: string; variant?: "default" | "secondary" | "outline" }Small badge above the heading
headingstringMain headline
descriptionstringSupporting 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
labelsLabelsText overrides for every field label, placeholder, and section heading in the card
currentStepnumber1Display-only step number used in the step label
totalStepsnumber4Display-only total step count used in the step label
classNamestringExtra classes for the outer <section>
ts
type Labels = {
  stepOf?: string;
  workspaceName?: string;
  workspaceNamePlaceholder?: string;
  workspaceUrl?: string;
  workspaceUrlPlaceholder?: string;
  urlPrefix?: string;
  inviteHeading?: string;
  inviteDescription?: string;
  emailPlaceholder?: string;
  addAnother?: string;
};

Behavior notes

  • The email invite rows are the only genuinely interactive part of the block: 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.
  • Workspace name and URL are plain uncontrolled 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.
  • Every label and placeholder in the card falls back to a hardcoded default inline in JSX via 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.
  • The workspace URL field uses 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.
  • There is no submit handler anywhere in the component: both 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.

More Onboarding blocks

View all Onboarding
PRO

onboarding37

Invite Your Team

A team setup section pairing a soft panel with a working invite row, a role picker, and a plain-language table of what each role can reach, with a bordered list of who is already on the account and whether they have accepted, closing on a seat meter that fills one tick per seat taken.

FREE

onboarding43

Guided Workspace Setup

A two-column setup section: the pitch and what each answer changes on the left, and a one-question-at-a-time wizard on the right that ends in a review of everything it is about to create.

PRO

onboarding19

Profile Setup Card

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.

PRO

onboarding29

Company Info Form

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.

PRO

onboarding23

Security Setup

Onboarding screen for configuring account security including two-factor authentication, recovery email, and backup codes. Perfect for apps that prioritize security during onboarding.

PRO

onboarding15

Integration Connector Grid

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.