- 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.
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.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.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.
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:
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
SAML and SCIM settings
The values to enter in any SAML 2.0 identity provider, and how SCIM maps your people.
Example: Microsoft Entra
The whole setup step by step in Entra’s generic SAML application.
SSO without SCIM
Use SSO sign-in and manage people in Connectly yourselves.
Troubleshooting
Common errors, and what to do after go-live.
