dialnote supports single sign-on through three major identity providers: Google, Microsoft, and Apple. Your team can skip passwords entirely and sign in with the accounts they already use every day.

Supported Providers#

All three providers work for both signing up and signing in. There's no separate setup or configuration needed — they're available on the login page right away.

How Social SSO Works#

When a team member clicks "Sign in with Google" (or Microsoft or Apple), here's what happens:

1. Redirect — dialnote sends them to the provider's login page.
2. Authenticate — They sign in with their existing provider credentials (and any 2FA the provider requires).
3. Return — The provider redirects them back to dialnote with a verified identity.
4. Session created — dialnote creates a secure session that lasts 7 days and refreshes automatically with activity.

The whole process takes just a few seconds. No extra passwords to remember, no separate credentials to manage.

Setting Up SSO for Your Team#

There's no admin configuration required. Every dialnote workspace has Google, Microsoft, and Apple sign-in enabled by default. To get your team started:

1. Invite team members — Go to Settings → User Management and send invitations.
2. Share the login page — Team members can choose any sign-in method when they accept the invitation.
3. Pick a provider — Each person clicks their preferred provider on the sign-in screen.

Team members can use different providers. One person might sign in with Google while another uses Microsoft — it all works within the same workspace.

Automatic Account Linking#

dialnote treats Google, Microsoft, and Apple as trusted identity providers. This means:

• If someone signs up with email/password first and later signs in with Google (using the same email), both methods link to the same account.
• If someone signs up with Google and later tries Microsoft (same email), those link together too.
• Account linking only happens when the email address is verified by the provider.

This prevents accidental duplicate accounts and lets people switch between sign-in methods without losing access.

Security Benefits#

Social SSO adds several layers of protection beyond a standard password:

• Provider-level security — Your team gets the benefit of Google's, Microsoft's, or Apple's security infrastructure, including their fraud detection and account protection.
• Centralized 2FA — If your company requires two-factor authentication through your identity provider, that protection carries over to dialnote sign-ins.
• No password to leak — With social SSO, there's no dialnote-specific password that could be compromised in a phishing attack or data breach.
• Automatic deprovisioning — If you disable someone's Google or Microsoft account, they can't use it to sign into dialnote anymore.

Troubleshooting#

"Account already exists" error — This usually means the email is already registered with a different sign-in method. Try signing in with email/password first, then link the social provider from your account settings.

Redirect loop or blank page — Clear your browser cookies for dialnote and try again. Pop-up blockers can also interfere with the OAuth flow — make sure your browser allows pop-ups from dialnote.

Wrong account selected — If your browser auto-selects the wrong Google or Microsoft account, sign out of that provider first, then try the dialnote login again.