> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connectly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise SSO

> Let your team sign in to Connectly with your company account over SAML 2.0, and manage their Connectly accounts from your identity provider with SCIM 2.0 🔐

Enterprise SSO lets your people sign in to Connectly with their company account. It is built on two standard protocols, so it is designed to work with any identity provider that supports them:

* **SAML 2.0 for sign-in.** Your identity provider checks who the person is, with your own MFA and access policies, and Connectly lets them in.
* **SCIM 2.0 for provisioning (optional).** Your identity provider creates Connectly accounts for the people you assign, and removes their access when you unassign or disable them.

Connectly uses the standard protocols, not a provider-specific integration, so the setup is the same for every provider. The [Microsoft Entra example](https://docs.connectly.ai/enterprise-sso/microsoft-entra.md) walks through it end to end with Entra's generic SAML application.

***

## Supported identity providers

Connectly has tested enterprise SSO end to end with Microsoft Entra ID and Keycloak. Other identity providers that support SAML 2.0, such as Okta, Google Workspace, OneLogin, ADFS or PingFederate, are set up the same way: tell Connectly which one you use before you start.

Automatic provisioning also needs a provider that can send SCIM 2.0 requests to a custom application, as Microsoft Entra ID and Okta can. If yours cannot, use [SSO without SCIM](https://docs.connectly.ai/enterprise-sso/without-scim.md).

> [!WARNING]
>
> Sign-in must go through SAML 2.0. OpenID Connect (OIDC) is not supported. In Microsoft Entra, this means your IT creates an **Enterprise application** with SAML single sign-on, not an **App registration**.

***

## What your people get

* People you assign in your identity provider sign in to Connectly with their company account and open the Connectly business linked to your connection.
* SSO is added next to the other sign-in methods. A person who also has a Connectly password or Google sign-in can use either. SSO cannot yet be made the only way in.
* Your identity provider's MFA and access policies apply at its sign-in. If your Connectly business requires MFA, people may also be asked for Connectly's second factor.

***

## Before you start

Check these before your IT opens your identity provider. The sign-in name and email rows cause most failed sign-ins.

| Topic | What is needed | If it is not met |
| - | - | - |
| Email domain | Your company's own domain, for example `acme.com`. Connectly verifies it for your connection: you publish a DNS TXT record, or Connectly reviews other proof that you own it. A domain belongs to one Connectly connection. | Public mail domains such as `gmail.com` or `outlook.com` cannot be used for enterprise sign-in. |
| Admin access | Someone who can create and configure applications in your identity provider. | Ask your identity provider administrator to do the setup. |
| Sign-in name | The SAML Name ID and the SCIM `userName` send the same value: the person's sign-in name, such as the user principal name in Microsoft Entra or the username in Okta. Most providers do this by default. | People your identity provider provisioned cannot sign in (Connectly shows `error=jit_disabled`). |
| Email address | Each person needs an email address in the sign-in and in SCIM. | Connectly cannot accept the person. Send the sign-in name as the email if people have no mailbox. |
| Who can sign in | Only people your identity provider has provisioned, or people an Owner added in Connectly when you do not use SCIM. | Anyone else is refused. With SCIM, the error is `error=jit_disabled`. Without SCIM, Connectly shows "Sign-in was not completed" with `error=access_denied`. |

***

## How setup works

**1. Request enterprise SSO**

Contact your Connectly account manager. Tell us your email domains, the Connectly business your people should land in and their role there (agent, marketing or analytics), whether you will use SCIM, and the name of one person for the first test sign-in.

**2. Connectly creates your connection**

Connectly creates a connection for your company, named for example `ent-yourcompany`, and hands its values to your IT in one of the two ways below. If you prove your domain by DNS, Connectly also sends you a TXT record to publish.

**3. Your IT sets up a SAML application**

Your IT creates a generic SAML 2.0 application in your identity provider with the values from Connectly, and assigns the people who will use Connectly. See [SAML and SCIM settings](https://docs.connectly.ai/enterprise-sso/saml-and-scim-settings.md).

**4. Connectly verifies your domain**

Connectly verifies your domain and links your connection to your Connectly business. You hear back when sign-in is switched on.

**5. Your IT sets up provisioning (optional)**

With SCIM, your IT enters the SCIM endpoint and token in your identity provider and checks the attribute mapping. Without SCIM, an Owner adds people in Connectly instead.

**6. Test with one person, then go live**

Provision one person, have them sign in through the Sign on URL in a private browser window, then start provisioning for everyone assigned.

***

## Two ways to hand over the values

Your IT's steps are the same both ways. Only these hand-overs differ:

| What | Setup link | Manual |
| - | - | - |
| Sign-in values for your identity provider | The setup wizard shows the Identifier and the Reply URL. The Sign on URL comes from Connectly. | Connectly sends all three. |
| Your identity provider's metadata | Paste your provider's metadata URL into the wizard. | Send the metadata XML file to Connectly. |
| SCIM endpoint and token | Copy the endpoint and generate the token yourself in the wizard. | Connectly sends the endpoint, and the token over a secure channel. |

**Setup link.** Connectly sends a one-time link to Auth0's setup wizard, which only offers SAML. The link works for the first person who opens it and expires after 24 hours if nobody does, so forward it unopened to the administrator who sets up your identity provider. When both parts of the wizard are done, click **Enable Connection** on its first page, confirm with **Proceed**, and tell Connectly.

**Manual.** Connectly sends the sign-in values and the DNS record first, and the SCIM endpoint and token once your metadata and domain are in. Copy them exactly, with no spaces at either end.

***

## Next steps

> [card] [SAML and SCIM settings](https://docs.connectly.ai/enterprise-sso/saml-and-scim-settings.md)
>
> The values to enter in any SAML 2.0 identity provider, and how SCIM maps your people.

> [card] [Example: Microsoft Entra](https://docs.connectly.ai/enterprise-sso/microsoft-entra.md)
>
> The whole setup step by step in Entra's generic SAML application.

> [card] [SSO without SCIM](https://docs.connectly.ai/enterprise-sso/without-scim.md)
>
> Use SSO sign-in and manage people in Connectly yourselves.

> [card] [Troubleshooting](https://docs.connectly.ai/enterprise-sso/troubleshooting.md)
>
> Common errors, and what to do after go-live.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.