Search blocks by description or jump to a page.
An account collision gate showing a Google sign in beside an existing password account, a link action, and a password sign in fallback.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Account Linking Page is the collision state reached when a Google sign in matches an email that already has a password account. The Acme lockup sits above a card headed This email already has an account, a line naming the address and the conflict, then a bordered panel with both identities stacked: the Google sign in verified just now, and the existing Acme account since 2023 with its workspace count and last active day. A Link Google to the existing account button leads, a Sign in with password instead button follows, and a footer note promises the link merges nothing and deletes nothing (one account, the same workspaces and history, plus Google as a method).
The two identity rows are static markup with a muted icon tile each. Showing both accounts side by side, and stating that nothing is merged or lost, is what turns a scary duplicate warning into a one-tap decision.
Reach for this block when an OAuth callback returns an email that already maps to a local account. Wire the link button to a flow that reauthenticates the password account once, then attaches the OAuth identity to it.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the Google to password collision. Other linking variants:
Tip: show both identities and say plainly that nothing merges or deletes; an account collision with no detail reads as a takeover and gets abandoned.