Connect an identity provider
Summary
Connecting an identity provider lets people sign in through your existing SSO (Okta, Microsoft Entra, ADFS, Google Workspace, or any standards-compliant OIDC/SAML provider) instead of a platform-specific password. This step completes when the connection is made and confirmed working.
Before you start
This step requires Ultimate. If your plan doesn't include it, this step shows in its normal place on your Identities checklist: grayed out, with a lock and the caption Not in your plan. It isn't clickable through, and it's excluded from your onboarding progress calculation entirely, so you can still complete the Identities milestone without it.
If your plan includes it, you need the Manage Tenant permission to set up People & access → Identity provider, plus administrator access on the identity provider side to configure the connection there.
1. Configure Single Sign-On
- Go to People & access → Identity provider → Single sign-on.
- Choose your provider type (OIDC or SAML) and enter its connection details.
- Map your provider's groups or claims to roles in this platform, so people land with the correct access on first sign-in.
- Save and test the connection before enforcing it for everyone.
If your identity provider is Google Workspace, Directory sync is a related but separate setting on the same page: it keeps your user roster in sync (added, updated, deactivated) rather than handling sign-in itself. You can sync on demand, or turn on Sync the directory every day; a large drop in people is never applied automatically, it waits for you to review it and shows in your Inbox.
2. Consider enforcement carefully
SSO enforcement blocks password and Google sign-in for everyone except administrators who manage the organization's settings once turned on. It requires an explicit risk-acknowledgment prompt before you can enable it. If SSO later breaks and nobody can sign in, support can give you a break-glass link to turn enforcement off (see Before you turn on enforcement below). Test the connection thoroughly with a non-admin account before enforcing.
Confirm it worked
Sign in through your identity provider (ideally with a test account first) and confirm you land in the platform with the role your group/claim mapping intended.
Before you turn on enforcement
Enforcement is a separate switch (Require single sign-on) from having SSO configured, shown as Required or Not required. Turning it on blocks password and Google sign-in for everyone except administrators who manage the organization's settings.
If SSO then breaks, you will need an administrator who signs in with a password, or a break-glass URL from support, to disable enforcement. The break-glass URL is not something you can generate yourself.
There is a Break glass: stop requiring now control on this page, but it only helps while you can still sign in: it appears only when enforcement is on, and reaching it means signing in, which enforcement blocks for everyone but password-holding administrators. Treat it as a way to reverse a decision you have just made, not as your recovery plan.
Test sign-in with a real account before enabling enforcement, and know who to contact if it fails.
If it didn't work
- You're locked out of CyberHQ.ai: sign in as an administrator who uses a password, or contact support for a break-glass URL. A broken SSO configuration stops everyone else signing in, and every in-product control is behind sign-in. You can't generate the URL yourself.
- You still have a working session open: you can use Break glass: stop requiring now on this page before that session expires. Existing sessions persist until they expire normally, so this window is real but limited.
- "Paste the IdP metadata XML or enter its URL." (when adding a SAML provider) or "Provide the identity provider metadata, either as a metadata URL or as pasted XML." (when saving a change to one): no metadata was supplied, or the change would leave none. Give the metadata XML or its URL.
- The SP signing certificate has expired: the page reports this. Select Replace signing certificate, then upload the new service provider metadata to your identity provider straight away: the old certificate stops being used immediately.
- Sign-in fails through the provider: double-check the connection details entered here match what your provider issued, and that the test was run before enforcing.
- Signed in but with the wrong role: check the group/claim-to-role mapping; a group not mapped to any role typically lands someone with a default or no access.
- Locked out after enabling enforcement: see You're locked out of CyberHQ.ai above. Once you're back in, re-check your mapping before turning enforcement on again.
- The step is locked: confirm your plan; this requires Ultimate. Contact your account team if you want to upgrade.