Single Sign-On (SSO)
Managing dozens of employee passwords is a security risk. Cord offers Single Sign-On through SAML 2.0 for organizations on the Scale or Developer plan. Any identity provider that speaks SAML works — Google Workspace, Microsoft Entra ID / Azure AD, Okta, and others — configured as a SAML application on your IdP, not as a direct OIDC connection.
Configure SSO
- In Settings › Team & permissions › SSO, click Get started and choose whether your team’s roles are assigned in Cord or in your identity provider.
- Add your team’s email domain (for example
yourcompany.com) and create the TXT record Cord gives you in your DNS. Cord verifies it by querying the real DNS, every 20 seconds while the panel is open; pasting the code on screen isn’t enough. - Create the configuration in four steps: paste your provider’s details (identity provider URL, issuer ID, and certificate, or the metadata XML), copy Cord’s ACS URL and Entity ID into your provider, test with the email of someone on your domain, and choose the domains and roles. The test checks your provider’s response step by step without starting a session and tells you what to change if something doesn’t match.
Once the configuration is on and tested, you can turn on Require SSO: password, Google, and passkeys stop working for your organization’s members, and Cord sends them to your identity provider. The account owner always keeps the option to sign in with a password, as an emergency exit if the identity provider goes down.
The requirement belongs to your organization, not to the sign-in: someone who also belongs to another organization with its own SSO can’t sign in through that one and then switch to yours. When they open your organization, Cord asks them to sign in with your identity provider.
If you allow sign-in from your provider’s app portal (Okta, Microsoft MyApps), Cord shows the email the person is about to sign in with and asks them to confirm with Continue, because that sign-in didn’t start in their browser.
If you have subaccounts grouped under a main account, SSO is set up only in the main account and applies to the whole tree. In a subaccount, Settings › SSO shows Managed by with the main account’s name; connections and Require SSO are changed from there.
What’s automated and what isn’t
Cord supports JIT provisioning (Just-In-Time): the first time someone from your domain signs in via SSO, Cord creates their account and membership automatically, without you having to invite them by hand. Cord does not support SCIM: removing someone from your directory (Google Workspace, Azure AD) does not automatically revoke their access to Cord — for that, revoke it as well from Settings > Team in Cord.