SSO setup
SSO — single sign-on — lets your people access Rival with the same company login they already use for everything else, instead of a separate Rival password. SAML is the common standard that makes this work between Rival and your identity provider.
Why enterprises want SSO
Section titled “Why enterprises want SSO”SSO is a security and convenience win at once. Convenience: one login, no new password to manage. Security: access is controlled centrally by your identity provider, so when IT disables someone’s company account, their Rival access goes with it — no orphaned logins. For most enterprises, SSO is a requirement, not a nice-to-have.
Connecting your identity provider
Section titled “Connecting your identity provider”At a high level, you connect Rival to your identity provider (IdP) — such as Okta, Microsoft Entra ID (Azure AD), or Google — by exchanging configuration between the two so each trusts the other. Once connected, your people sign in through your IdP and land in Rival. [VERIFY: confirm which identity providers are supported and the exact setup steps.]
SSO and roles
Section titled “SSO and roles”SSO handles who can sign in. Their Rival role still governs what they can do once they’re in — the two work together. See Roles & Permissions.
A quick example
Section titled “A quick example”A company connects Rival to Okta. New hires already provisioned in Okta can sign straight into Rival with no separate account; when someone leaves and IT deactivates their Okta account, their Rival access ends automatically. Access follows employment, managed in one place.