SSO and SCIM

Your directory decides who's in

Connect your identity provider to your Cal.com organization. People sign in with SAML or OIDC, join the teams their directory groups map to, and leave when you deactivate them.

Trusted by fast-growing companies around the world

Acme connects Okta

Martin runs IT at Acme. Follow him from the SAML dialog to Tobias's first day in Sales, and to Pieter's last day in Support.

Single sign-on

Paste Okta's SAML metadata

Martin opens SSO with SAML and pastes the metadata from Okta. Cal.com saves the connection and shows the ACS URL and Entity ID he copies back into Okta.

Directory sync

Point Okta at Cal.com

He names the directory Acme Okta and picks Okta SCIM v2.0. Cal.com gives him a SCIM Base URL and a Bearer Token, the two things Okta asks for.

Directory sync

Map groups to teams

Under Teams, Martin adds the Okta group Sales to the Sales team and Support to Support. Onboarding has no group yet, so nobody joins it from Okta.

Members

Tobias starts in Sales

HR puts Tobias, a new hire, in the Sales group in Okta. Cal.com creates his account in Acme, adds him to the Sales team and emails him an invite.

Members

Pieter leaves Support

On Pieter's last day, Martin deactivates him in Okta. Cal.com removes him from Acme, from Support and from the team's event types.

Cal.ai

Ask who's on the team now

Cal.ai lists a team's members as directory sync left them, so you can check a change landed.

Watch it set up

A short recording of Okta going from the SAML dialog to its first synced team member, in the same steps as above.

Tutorial0:49

In this video

Questions about SSO and SCIM

Which providers work, who can set it up and what syncs.

Ask a question

Let your directory manage members

Connect Okta or any SAML, OIDC or SCIM provider to your organization.

Get startedTalk to sales