LifeLeveled helps you master career readiness, financial literacy, and confidence with 8 essential pages and AI coaching for skill development.

Institutional Documentation

Single Sign-On (SSO)

Last updated: September 2026Documentation status: In development

LifeLeveled supports secure email-and-password authentication and OAuth sign-in through Google, Microsoft, Apple, and Facebook for all users. These methods are fully operational today.

Institution-managed enterprise SSO through SAML 2.0 and OpenID Connect is on the product roadmap and is not yet operational.

Important: Enterprise SSO is a planned feature, not a current capability. Universities and institutions may contact info@lifeleveled.org to discuss identity provider requirements, configuration, provisioning, security review, timelines, and testing. LifeLeveled would collaborate with the institution's teams before representing enterprise SSO as configured or operational.

Current Authentication Methods

The following authentication methods are fully operational for all users today:

Email and password. Users can create accounts and sign in using email and password, with credential storage managed by the platform's authentication infrastructure.
Google OAuth. Users can sign in with their Google account.
Microsoft OAuth. Users can sign in with their Microsoft account.
Apple OAuth. Users can sign in with their Apple ID.
Facebook OAuth. Users can sign in with their Facebook account.

Enterprise SSO Roadmap

LifeLeveled is developing support for institution-managed enterprise SSO through the following standards:

SAML 2.0. For institutions using SAML-based identity providers such as Active Directory Federation Services (AD FS), Okta, OneLogin, and Ping Identity.
OpenID Connect (OIDC). For institutions using OIDC-based identity providers such as Google Workspace, Microsoft Entra ID (Azure AD), and Auth0.

Enterprise SSO would allow institutions to manage user access through their existing identity provider, enforce institutional authentication policies, and streamline onboarding for large user populations.

Institutional Configuration Process

When enterprise SSO becomes available, the configuration process would involve:

Identity provider metadata exchange and trust configuration
Attribute mapping (email, name, role) from the institutional IdP
User provisioning and de-provisioning workflows
Security review of the SSO configuration by the institution
Pilot testing with a small user group before full deployment

Until enterprise SSO is operational, institutions can use the current OAuth providers or email/password authentication for their users.

Contact

Universities and institutions may contact info@lifeleveled.org to discuss SSO requirements, timelines, and implementation planning.