Symptoms
- Your company uses single sign-on (Okta, Microsoft Entra ID, Google Workspace, or another identity provider) and you want seeo access managed through it
Cause
This is a capability question, not a fault: seeo supports enterprise single sign-on by federating your identity provider, so your team signs in with their normal work credentials and your IT team keeps control of access.
Resolution
- Ask your IT team to contact seeo support to set up the federation — it is configured once per organization, using standard OpenID Connect or SAML.
- Once federated, your team signs in to seeo by choosing the single sign-on path and entering their normal work credentials.
- Joiners and leavers are then governed by your identity provider: disable someone there and their seeo access ends with it.
Verification
A team member signs in via your identity provider and lands on your organization's sites; a disabled test account can no longer sign in.
Escalate if
Sign-in works but a user lands without their expected sites — the role mapping needs adjusting.