Skip to content
Design System
GitHub

Sign-in

Getting in: company SSO first, an email link as the fallback, the 2FA code step, and what happens next.

Overview

When to use

  • The sign-in page of an internal tool or console.
  • The second step after a password: a code from an authenticator app or a recovery code.

Blocks

Sign in

Company SSO first, email link as the fallback; one column, errors under the field, a confirmation that says where the link went.

Install
npx shadcn add @syncrobotic/sign-in

Passkey sign-in

Sign in with a passkey, with a code from an authenticator app as the way back in on the same page.

Install
npx shadcn add @syncrobotic/auth-passkey

Accept an invitation

Who invited you, to what, and what the role lets you do, then one field and one action to join.

Install
npx shadcn add @syncrobotic/auth-invite

Two-factor sign-in

The step after the password: a 6-digit code or a recovery code, remember this browser for 30 days, errors and a pause in words, a passkey as the quicker way.

Install
npx shadcn add @syncrobotic/auth-2fa

Usage rules

  • The way most people sign in is the first button.
  • Errors sit under the field they are about and never clear what was typed.
  • A wrong code says how many tries are left; a pause says how long, and the button counts it down.