Introduction to the SSO Implementation
Single Sign-On (SSO) allows your team and community members to access the platform using their existing corporate credentials. This streamlines the login experience, improves security by centralizing authentication, and reduces password fatigue across your organization.
Simplify access and enhance security by integrating your organization’s identity provider. This enables seamless login for users while maintaining centralized control over authentication and account security across your entire ecosystem.
Plan Availability: This feature is exclusively available for users on the Enterprise Plan. If you are on a different plan, please contact your Customer Success Manager to upgrade your subscription.
The SSO configuration is a backend process managed by the AcceleratorApp technical team. Unlike other self-service integrations, this requires backend activation to ensure secure and stable connectivity with your identity provider (IdP). Once the backend setup is complete, the configuration status can be reviewed by your Super Admins.
Where to Find SSO Implementation
Because this requires backend activation, the setup is initiated by gathering your credentials and reaching out to our support team, after which Admins can verify the active status in the platform settings.
Step-by-Step
1. Identify Your Identity Provider and Authentication Method
Determine which Identity Provider (IdP) your organization uses (e.g., Okta, Microsoft Entra ID / Azure AD, Google Workspace) and the authentication protocol you will use (such as SAML 2.0 or OpenID Connect).
2. Gather Technical Metadata from Your Identity Provider
Gather the required technical details based on your chosen provider and protocol. For SAML integrations, you typically need to copy the SAML 2.0 Endpoint
3. Submit a Backend Configuration Request to Support
Provide the gathered metadata and identity provider details to the AcceleratorApp support or technical team. We will use this information to configure the connection on the backend, map the necessary attributes (such as ensuring the email address is the primary identifier), and enable the secure link.
Coordinate the Connection Testing Phase
Perform a live, coordinated test login alongside the AcceleratorApp technical team using a dedicated test account. This ensures the authentication handshake functions correctly and prevents users from being locked out.Verify Domain Enforcement Rules
Confirm with the AcceleratorApp technical team which specific email domains (e.g., @yourcompany.com) must be forced to authenticate exclusively through your SSO link.Confirm Go-Live Activation
Verify that the integration is fully live. Your community members can now officially log into AcceleratorApp using their centralized corporate credentials.
Best Practices
Coordinate Launch Communication: Send an update to your founders, mentors, and team members before turning on domain enforcement, as they will transition from their old platform-specific passwords to their corporate credentials.
Reach Out for Any Infrastructure Changes: Because this is a backend-managed feature, remember to contact our support team well in advance whenever your internal security team changes your endpoints, certificate rotations, or security settings.
Don't Assume Protocol Uniformity: Always clarify your specific identity provider setup in step 1 before gathering data, as requirements change depending on whether you use SAML or another connection type.