Social connections

Atlas supports 56 social / OAuth connections — Google, GitHub, Microsoft, Apple, Slack, Discord, GitLab, LinkedIn, Facebook, Twitch, X, Spotify, Notion, Figma, Salesforce, Shopify, Steam and many more. One integration, and every account your users already have flows into a single identity.

Add a provider

1. Open Connections → Social for your instance.

2. Choose a provider (for example, Google).

3. In Development, you can use Atlas's shared credentials to try it instantly. In Production, create an OAuth app with the provider and paste its client id and client secret.

4. Register this redirect / callback URL with the provider:

https://atlasauth.net/v1/oauth/callback/<provider>

(Replace <provider>, e.g. google. If you use a custom domain, use that host instead.)

1. Choose the connection's scope: sign-in, sign-up, or both.

2. Save and test from your sign-in page.

What "one identity" means

When a user signs in with Google and later with GitHub using the same verified email, Atlas can link both to one user rather than creating duplicates. You control account-linking behavior in the dashboard.

Google One-Tap

Google additionally supports secretless One-Tap — a streamlined prompt that signs users in without a full redirect. Enable it on the Google connection.

Provider tips

• Apple requires a Services ID and a signing key rather than a simple secret — the dashboard walks you through it.

• Some providers (e.g. Steam, Slack) return limited profile data; Atlas maps what's available to the user profile.

• You can enable a provider for sign-up only (existing users keep their current method) or sign-in only.

Security

Atlas binds the OAuth state to the session and checks the redirect against an exact-origin allowlist, so authorization codes can't be replayed or redirected to an attacker. Provider secrets are held encrypted at rest.

Next

Offer phishing-resistant sign-in with no password at all → Passkeys.