Company sign-in (SSO)
Let your team sign in to OmniLab with their company account instead of an emailed sign-in link.
With single sign-on (SSO), your team signs in to Studio with their company account, such as Microsoft. Your IT team prepares the connection, and your Customer Success Manager turns it on.
Supported providers
| Provider | Best fit |
|---|---|
| Microsoft Entra ID (Azure Active Directory) | Companies that already use Microsoft accounts |
| Salesforce Marketing Cloud | Teams that already sign in to Marketing Cloud |
For any other provider, ask your Customer Success Manager before you plan a rollout.
Your IT team registers OmniLab in your identity system and collects the details to share. Send them Connect your identity provider.
Prepare the accounts in OmniLab
Before you test sign-in, for each test user:
- Create their account, with the email address your identity system returns.
- Assign them to at least one organisation.
- Set their sign-in method to company single sign-on. Until then, they get a Wrong sign-in method message.
The Authentication tab in Organization Settings is for participants' double opt-in, not for your team's sign-in.
Roll it out gradually
Each account signs in one way. A user moved to single sign-on can no longer use an email link, even while email sign-in stays on for your environment. So move people in stages:
- Leave email sign-in on.
- Move a small pilot group, and check they land in the right organisation.
- Move everyone else in batches.
- Ask your Customer Success Manager to turn email sign-in off once everyone has moved.
If a pilot user gets stuck, an admin can put that account back on email sign-in.