Skip to main content
Once a user is signed in, you can let them attach additional social identities to the same account — and remove them later. This is separate from sign-in: see Authenticate with Social for the initial OAuth flow. Enable Social Account Linking in the dashboard under Login & User Profile before exposing this in your UI. Make sure each provider you offer is fully configured (client ID, secret, redirect URI).

Listing linked accounts

getUserSocialAccounts returns the user’s currently linked social credentials, derived from user.verifiedCredentials filtered to OAuth-format entries.

Linking a new account

To attach an additional provider to a signed-in user, use the same signInWithSocialRedirect flow as sign-in. When called by an authenticated user, it adds the new credential rather than starting a new session.
See Authenticate with Social for the complete OAuth round-trip.

Unlinking an account

unlinkSocialAccount removes a single linked credential identified by verifiedCredentialId (read it from getUserSocialAccounts).

Supported providers

The SocialProvider type covers: apple, discord, facebook, github, google, kraken, linkedin, microsoft, epicgames, steam, tiktok, twitch, twitter. Each provider must be enabled and configured in the dashboard. See the social providers overview for per-provider setup.

Notes

  • getUserSocialAccounts requires an authenticated user — it throws if user is undefined. Guard the call by checking dynamicClient.user (see Check if signed in) or user from React hooks first.
  • Unlinking does not sign the user out, even when removing their original sign-in provider — provided they have at least one other credential (a wallet or another social account). The API returns a VerifyResponse updating the user’s verified credentials.
  • Linking a new account does not change the user’s primary sign-in method. To change which credential the user authenticates with next time, see the authentication methods overview.
Last modified on June 24, 2026