Creating an Account
Creating a SingleSign account is free and takes less than a minute. Follow these steps to get started.
Step-by-step
- Go to singlesign.com and click "Sign up free".
- Enter your email address and choose a password. Pick a strong, unique password that you don't use on other websites. If you arrived from an app's invitation email, your email address is already filled in and can't be changed — the invitation is tied to that address.
- Check your email for a verification link. It usually arrives within a few seconds. If you don't see it, check your spam or junk folder.
- Click the verification link in the email to confirm your account.
- You're all set! You can now use your SingleSign account to sign in to any app that supports SingleSign.
Tips for a strong password
- Use at least 8 characters, including at least one symbol.
- Longer passwords with a mix of letters, numbers, and symbols are even stronger.
- Avoid common words, birthdays, or easily guessable information.
- Consider using a password manager to generate and store your password securely.
What happens after you sign up?
Once your account is verified, you can:
- Sign in to apps that support SingleSign using your new account.
- Enable multi-factor authentication (MFA) for extra security. We strongly recommend this. Learn how to enable MFA.
- Manage your profile to control what information apps can see when you sign in.
Didn't receive the verification email?
- Check your spam or junk folder.
- Make sure you entered the correct email address.
- Try clicking "Resend verification email" on the sign-up page.
- If you're still having trouble, see our troubleshooting guide.
Last updated: 2026-08-04
Related articles
- Help CenterFind answers about using SingleSign to sign in, manage your privacy, and secure your account.
- Account Security, step by stepAn overview of how to protect your SingleSign account with MFA, backup codes, session management, and recovery options.
- free identity providerSingleSign pricing in one line: sign-in is free, with no monthly-active-user meter. See exactly what is included, and what SingleSign Mail costs for businesses.
- Identity provider alternativesIdentity provider alternatives, by the provider you are leaving: what actually has to change in your code, and what does not.
- Auth0 comparisonSingleSign vs Auth0 compared on the difference that matters: who owns the account. A side-by-side table, then the three cases where each one is the right call.
- Okta comparisonSingleSign vs Okta: Okta is built for workforce identity inside a company, SingleSign for consumer sign-in across applications.
- SingleSign vs Firebase AuthenticationSingleSign vs Firebase Authentication on lock-in, portability and consent, plus the cases where staying on Firebase is right.
- Google Sign-In alternativeSingleSign vs Google Sign-In: the same one-tap convenience, without an advertising business behind the identity.
- alternative to Auth0Auth0 alternatives compared, plus the part most listicles skip: what migrating off Auth0 actually involves, which code changes, and which does not.
- Okta alternativesOkta alternatives for teams that need customer sign-in rather than workforce identity. The table first, then what changes when you move consumer auth off Okta.
- alternative to Firebase AuthFirebase Authentication alternatives for teams leaving Google Cloud or wanting a standalone OIDC provider. Comparison table, then the real migration path.
- SaaS single sign-onSSO for SaaS applications using OAuth 2.0 and OpenID Connect: the flow to pick, the scopes to request, and a working integration path with SingleSign.