Signing In to an App with SingleSign
When an app supports SingleSign, you can use your SingleSign account to sign in instead of creating a new username and password. Here's how it works.
Step-by-step
-
On the app's login page, click "Sign in with SingleSign." This button may also appear as "Continue with SingleSign" or display the SingleSign logo.
-
You'll be redirected to SingleSign. This is the secure SingleSign sign-in page where you enter your credentials.
-
Enter your email and password. If you arrived from an app's invitation email, your email address is already filled in and can't be changed — just enter your password. If you've enabled multi-factor authentication (MFA), you'll also be asked to enter the 6-digit code from your authenticator app.
-
Review what the app is asking to access. SingleSign will show you the specific information the app is requesting — for example, your email address or display name. This screen only appears the first time you sign in to an app (or if the app requests new permissions).
-
Click "Allow" to grant access. Only approve permissions you're comfortable sharing. You can always revoke access later.
-
You're redirected back to the app, signed in. That's it — you're now using the app with your SingleSign identity.
Returning visits
After you've approved an app for the first time, future sign-ins are faster. You'll typically just enter your SingleSign credentials (and MFA code if enabled) and be redirected back immediately — no need to re-approve permissions unless the app requests additional access.
Signing out
Signing out of an app does not sign you out of SingleSign. If you want to sign out of SingleSign itself, go to singlesign.com and click "Sign out" in your account menu.
Tips
- Bookmark singlesign.com so you can quickly access your account settings.
- Enable MFA to protect your account even if someone learns your password. Set up MFA now.
- Review connected apps regularly to make sure you recognize all the apps you've authorized. Manage connected apps.
Last updated: 2026-08-04
Related articles
- Help CenterFind answers about using SingleSign to sign in, manage your privacy, and secure your account.
- Managing Connected Apps, step by stepHow to view, review, and revoke the apps connected to your SingleSign account.
- Google Sign-In alternativeSingleSign vs Google Sign-In: the same one-tap convenience, without an advertising business behind the identity.
- 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.
- SingleSign vs OktaSingleSign vs Okta: Okta is built for workforce identity inside a company, SingleSign for consumer sign-in across applications.
- Firebase Auth comparisonSingleSign vs Firebase Authentication on lock-in, portability and consent, plus the cases where staying on Firebase is right.
- 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.