Team Invitation

Invite teammates, assign the right role and team, track seat usage, and resolve pending or expired invitations without losing context. The screen connects Members and Invitations so workspace admins can find the “Send invites” action while checking seats used and pending invites.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Maya Chen · Admin · Product and Jon Bell · Member · Engineering, rather than an empty visual shell.

Team Invitation
Use this template in Figr

Template facts

Screen

Form

Primary action

Send invites

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Workspace admins need a clear “Send invites” action without losing sight of seats used, pending invites and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Send invites is clearly available where the task happens.
  • Main view: Members keeps the starting point obvious.
  • Connected view: Invitations supplies nearby context.
  • Metric: Seats used is visible with a meaningful value.
  • Another signal: Pending invites helps people judge what to do next.
  • Representative record: Maya Chen · Admin · Product makes the example specific.
  • Second record: Jon Bell · Member · Engineering shows the pattern works beyond one item.

States worth designing

  • Missing required details; show what people can do instead of leaving a blank panel.
  • Loading members without changing the layout unexpectedly.
  • Invalid or conflicting entry; explain the problem and preserve work.
  • Permission denied for invitations; clarify who can continue.
  • Success after choosing Send invites; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Members → Invitations → Send invites → Review outcome

Patterns used

Form, Members, Invitations, Groups, accessible states, contextual actions

Why these choices work

Put requirements beside each field and show validation near the source of the error. Keep entered details if saving fails.

In this design, people should be able to compare Maya Chen · Admin · Product with Jon Bell · Member · Engineering. Make seats used clear, then use pending invites to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Send invites” action. The happy path alone is not enough.

Related UI examples: Account Creation, SSO Setup, Workspace Onboarding.

Start from this in Figr

Design a team invitation screen for our existing software product. Use our real design-system tokens, components and product language. Show Members and Invitations, include believable records such as Maya Chen · Admin · Product, and make send invites easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr