Managing Connected Apps
Every app you sign in to with SingleSign is added to your Connected Apps list. You can review these apps at any time and revoke access to any app you no longer trust or use.
How to manage connected apps
- Sign in to your SingleSign account at singlesign.com.
- Go to Account → Privacy → Connected Apps. This page shows all the apps you've authorized.
- Review the list of apps. Each entry displays:
- App name — the name of the app you authorized.
- Scopes granted — the categories of data the app can access (e.g., email, profile).
- Last access date — the most recent time the app used your SingleSign account.
- Check for apps you don't recognize. If you see an app you don't remember authorizing, it's a good idea to revoke its access.
- To revoke access, click "Revoke" next to the app you want to disconnect.
- The app will no longer be able to access your data. It will immediately lose its ability to read your information through SingleSign.
- If you sign in to that app again, you'll be presented with the consent screen and asked to re-approve the scopes it requests.
When should you revoke access?
- You no longer use the app.
- You don't recognize the app.
- The app is asking for more data than you're comfortable sharing (you can revoke and re-authorize with different scopes).
- You're doing a periodic security review of your account.
What happens when you revoke?
- The app immediately loses access to your data.
- You will not be signed out of the app automatically (the app may keep you signed in with an existing session).
- To fully disconnect, sign out of the app as well.
- If you sign in to the app again with SingleSign, you'll go through the consent process again.
Tips
- Review your connected apps regularly — we recommend checking at least once a month.
- Revoke apps you don't recognize immediately and consider reviewing your active sessions for any unauthorized access.
- Enable MFA to add an extra layer of protection. Learn how.
Last updated: 2026-02-16
Related articles
- Help CenterFind answers about using SingleSign to sign in, manage your privacy, and secure your account.
- Google Sign-In alternativeSingleSign vs Google Sign-In: the same one-tap convenience, without an advertising business behind the identity.
- Signing In, step by stepHow to sign in to an app with your SingleSign account, what the consent screen is asking for, and what to do if sign-in does not finish.
- Privacy & Consent, step by stepUnderstand what apps can access, how consent works, and how to manage your data with SingleSign.
- the Scopes & Consent docsHow to request scopes, what data each scope grants, the consent UI, and the principle of least privilege.
- Secure sign-in for every platform.SingleSign is a free identity provider with OAuth 2.0 and OpenID Connect for developers, and per-app consent and instant revocation for everyone signing in.
- Privacy PolicyHow SingleSign collects, uses, and protects your personal information.
- 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.
- SingleSign vs Auth0SingleSign 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.