About SSO for your team
Let the people who build campaigns sign in to OmniLab with the company account they already use.
Single sign-on (SSO) — letting your team log in with their company account — removes the need for a separate OmniLab password. When an employee opens OmniLab, they click the company sign-in button and they are in, using the same credentials they use for other company tools.
Your IT team sets this up once in coordination with OmniLab, and it then applies to everyone in scope.
A colleague opens OmniLab Studio
They choose sign in with your company account
Your identity system checks who they are
The same screen and rules as your other business tools.
It confirms their identity to OmniLab
OmniLab opens with the access their role allows
Someone who has left the company is stopped at step 3, without anyone touching OmniLab.
A colleague opens OmniLab Studio
They choose sign in with your company account
Your identity system checks who they are
The same screen and rules as your other business tools.
It confirms their identity to OmniLab
OmniLab opens with the access their role allows
OmniLab never sees a password. It asks your identity system who this is, and trusts the answer.
Why use SSO for internal users
- No separate password for your team to manage or reset.
- User access is tied to your company's identity system — when someone leaves and their company account is disabled, their OmniLab access stops automatically.
- More consistent with the single sign-on experience your team expects from other business tools.
How to get started
Your IT team registers OmniLab as a trusted application in your company's identity provider (for example Microsoft Entra ID or Salesforce). They gather a small set of technical details and share them with your OmniLab Customer Success Manager, who then enables the feature for your environment.
Decide which provider to use
OmniLab supports Microsoft Entra ID (Azure Active Directory), Salesforce Marketing Cloud, and custom providers. Confirm with your IT team which one your organisation uses.
Have your IT team prepare the configuration
Your IT team registers OmniLab in your identity provider and collects the required details. Full technical instructions are in the single sign-on setup reference for developers.
Share the details with your Customer Success Manager
Send the collected details to your OmniLab Customer Success Manager. They will enable single sign-on for your environment and provide any final confirmation steps.
Verify users in OmniLab
Each person who will sign in via company single sign-on must already have an account in OmniLab and be assigned to at least one organisation. Sign-in only works for users whose OmniLab account already exists.
Their account also has to be set to sign in this way. Every OmniLab account is tied to exactly one sign-in method, so someone still set to email sign-in is turned away with a Wrong sign-in method message even after their company account authenticates them. An Admin changes this on the user.
Test with a small group first
Before rolling out to your whole team, test with two or three users. Confirm that the sign-in button appears, the provider authenticates correctly, and users land in the right organisation.