Troubleshooting
Having trouble with your SingleSign account? Find solutions to the most common issues below.
I didn't receive a verification email
If you signed up but didn't get the verification email:
- Check your spam or junk folder. Verification emails sometimes get filtered.
- Wait a few minutes. Email delivery can occasionally be delayed.
- Try resending the email. Go back to the sign-up page and click "Resend verification email."
- Double-check your email address. Make sure you entered it correctly during sign-up. A small typo (e.g.,
gmial.cominstead ofgmail.com) will prevent delivery. - Check if your inbox is full. Some email providers reject new messages when your inbox is at capacity.
If you've tried all of the above and still haven't received the email, contact support@singlesign.com for help.
I can't sign in
If you're unable to sign in to your SingleSign account:
- Check your password. Make sure you're entering the correct password. Passwords are case-sensitive.
- Try resetting your password. Click "Forgot password?" on the sign-in page to receive a password reset link.
- Check if your account is locked. After multiple failed sign-in attempts, your account may be temporarily locked for security. Wait 15 minutes and try again.
- Clear your browser cache and cookies. Sometimes stale data can interfere with sign-in.
- Try a different browser or device. This can help rule out browser-specific issues.
I lost my MFA device
If you've lost the device with your authenticator app and can't enter your MFA code:
- Use a backup code. On the MFA prompt, click "Use a backup code" and enter one of the codes you saved when you set up MFA.
- Reset MFA after signing in. Once you're in, go to Account → Security → MFA and set up MFA again with your new device.
- No backup codes? Contact your recovery contacts if you've set them up. They can help initiate an account recovery.
- No recovery contacts either? Contact support@singlesign.com. You'll need to verify your identity through an additional process.
To avoid this situation in the future, always generate and securely store backup codes.
An app is asking for too many permissions
If an app's consent screen is requesting scopes (data categories) you're not comfortable with:
- You can deny the request. Click "Deny" on the consent screen. You won't be signed in to the app, but your data stays safe.
- Review what the app is asking. Each scope is listed with a description. Learn what each scope means.
- Contact the app developer. If you think the app is requesting more data than it needs, reach out to the app's support team to ask why.
- Report the app. If you believe an app is misusing SingleSign, contact support@singlesign.com.
I want to delete my account
If you'd like to permanently delete your SingleSign account and all associated data:
- Revoke all connected apps first. Go to Connected Apps and revoke access for each app.
- Contact support. Send an email to support@singlesign.com with the subject line "Account Deletion Request."
- Verify your identity. You'll be asked to confirm your identity before the deletion is processed.
- Allow processing time. Account deletion is typically completed within 7 business days.
Note: Account deletion is permanent and cannot be undone. You will lose access to all apps connected through SingleSign.
Last updated: 2026-02-16
Related articles
- Help CenterFind answers about using SingleSign to sign in, manage your privacy, and secure your account.
- 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.
- Firebase Auth comparisonSingleSign vs Firebase Authentication on lock-in, portability and consent, plus the cases where staying on Firebase is right.
- SingleSign vs Google Sign-InSingleSign 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.
- alternative to OktaOkta 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.
- Firebase Authentication alternativesFirebase 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.
- Authentication for startupsAuthentication for startups without a monthly-active-user meter: standards-based OAuth 2.0 sign-in you will not have to replace when the product finds traction.