Workspace Transfer

Transfer workspace ownership with destination account, billing impact, member access, connected integrations, data responsibility, and confirmation safeguards. This example brings Destination and Ownership together so administrators and growth teams can find the next task without losing context.

It includes representative records such as Choose new owner and Review workspace data. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Workspace Transfer
Use this template in Figr

Template facts

Screen

Form

Primary action

Transfer workspace

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to transfer workspace while keeping members, projects and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Destination gives users an obvious place to start.
  • Supporting view: Ownership keeps the related context close.
  • Primary action: Transfer workspace stays visible when people need it.
  • First signal: Members shows a useful value (248).
  • Second signal: Projects gives additional context (42).
  • Sample record: Choose new owner.
  • Next record: Review workspace data.

States worth designing

  • Required field missing: say what changed, protect progress, and offer a clear next step.
  • Invalid value or incompatible data: say what changed, protect progress, and offer a clear next step.
  • Draft saved: say what changed, protect progress, and offer a clear next step.
  • Submitted for review: say what changed, protect progress, and offer a clear next step.
  • No permission to submit: say what changed, protect progress, and offer a clear next step.
  • Temporary save failure: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Destination → Ownership → Transfer workspace → Review outcome

Patterns used

Form, Destination, Ownership, contextual actions, error recovery

Why these choices work

Show requirements beside fields and retain values after failed checks. Validate only the affected input and make the next step unmistakable.

Pay attention to destination and ownership. People need to distinguish Choose new owner from Review workspace data. Keep members visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Transfer workspace”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Webhook Settings, Referral Program, Data Export Center.

Start from this in Figr

Design a workspace transfer screen inside our existing product. Use our current components, tokens and content language. Include Destination and Ownership views, credible records like Choose new owner, and a clear “Transfer workspace” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr