OpenID Authentication
Use OpenID authentication when your organization needs a managed sign-in flow instead of ad hoc personal accounts. This is the right path when identity, approval rules, and account lifecycle should follow your existing corporate provider.
Before you start
Section titled “Before you start”- Confirm which identity provider is the source of truth.
- Decide whether Hyper should allow mixed login methods or enforce managed identity only.
- Review join settings, required 2FA, and guest policy before pilot users start signing in.
Where it fits
Section titled “Where it fits”- Organization-wide sign-in policy.
- Restricted workspaces that should not allow unmanaged personal identity paths.
- Security reviews where admin control over authentication is required.
Recommended rollout pattern
Section titled “Recommended rollout pattern”- Connect and validate the provider in a pilot workspace.
- Test the full path for new members, returning members, and removed users.
- Confirm how workspace membership, team mapping, and meeting access behave after sign-in succeeds.
- Expand only after support knows how to diagnose identity mismatches.
Troubleshooting
Section titled “Troubleshooting”Sign-in succeeds, but the user lands in the wrong place
Section titled “Sign-in succeeds, but the user lands in the wrong place”- Check whether the provider assertion maps to the intended workspace identity.
- Confirm the user belongs to the right workspace or team after authentication.
- Review approval, domain, and guest rules if identity succeeds but workspace entry is still blocked.