SSO Setup

Connect an identity provider, map domains and claims, then test the connection before enforcing SSO. The screen connects Provider and Domains so workspace admins can find the “Test connection” action while checking domains and mapped groups.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Okta SAML connection and northstar.ai domain, rather than an empty visual shell.

SSO Setup
Use this template in Figr

Template facts

Screen

Form

Primary action

Test connection

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 “Test connection” action without losing sight of domains, mapped groups and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Test connection is clearly available where the task happens.
  • Main view: Provider keeps the starting point obvious.
  • Connected view: Domains supplies nearby context.
  • Metric: Domains is visible with a meaningful value.
  • Another signal: Mapped groups helps people judge what to do next.
  • Representative record: Okta SAML connection makes the example specific.
  • Second record: northstar.ai domain 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 provider without changing the layout unexpectedly.
  • Invalid or conflicting entry; explain the problem and preserve work.
  • Permission denied for domains; clarify who can continue.
  • Success after choosing Test connection; 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

Provider → Domains → Test connection → Review outcome

Patterns used

Form, Provider, Domains, Claims, 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 Okta SAML connection with northstar.ai domain. Make domains clear, then use mapped groups 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 “Test connection” action. The happy path alone is not enough.

Related UI examples: Team Invitation, Role Permission Setup, Account Creation.

Start from this in Figr

Design a sso setup screen for our existing software product. Use our real design-system tokens, components and product language. Show Provider and Domains, include believable records such as Okta SAML connection, and make test connection easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr