About this block

Invite Team Panel is the multi seat invite step: three email Input rows each paired with a closed role Select defaulting to Admin for the first row and Member for the rest, a ghost Add another button, and a muted callout that states the honest reason the ask sits here: workspaces with 2 or more members in their first week retain 3x better. The footer carries Send invites as the primary action and Skip for now as an outline button of equal visual weight.

Invite rows are a small array; roles are a separate const. The retention stat in the callout is not marketing copy, it is the actual reason the form exists at onboarding rather than buried in settings.

When to use

Reach for this block as the invite step in an onboarding flow, wired to your invite endpoint and role model. Show the callout only on first encounter; suppress it when the user already has teammates in the workspace.

A natural flow around it on an Application Pro page:

Before

• Setup progress stepper

After

• Connect source card
• Users table

What you can display

One strong use is the team invite step during workspace setup. Other invite panels:

• Project level invite. The same shape scoped to one project with viewer, editor, and admin roles.
• Bulk import. A textarea variant for pasting a CSV of emails instead of individual rows.
• Pending invites list. The same panel post send with resend and revoke actions per row.

Tip: invites expire after 7 days; printing that once in the description prevents the how do I resend support ticket before it arrives.