Set up single sign-on and SCIM
Verify your company domain, connect a SAML identity provider such as Okta or Entra ID, and provision people automatically with SCIM.
On this page
Single sign-on (SAML) lets people sign in through your identity provider, such as Okta, Microsoft Entra ID or Google Workspace. SCIM lets that provider add, update and remove people for you. Both live in Settings → Identity and only apply to people at verified domains.
1. Verify your domain
- Under Domains, enter your company's email domain, like acme.com, and click Add domain.
- Add the TXT record shown at your DNS provider, or choose Copy instructions for IT from the domain's menu.
- Click Check now. DNS changes can take up to an hour.
Once a domain is Verified, you can turn on Add people at verified domains so anyone signing in with that domain joins the workspace.
2. Connect single sign-on
Only owners can change single sign-on. Admins can view it and run a test.
- Create a SAML app in your identity provider. Copy in the ACS URL and Entity ID from Details for your identity provider. Send the email address as the NameID, plus firstName and lastName attributes.
- Back in Vidler, choose Import metadata and paste the metadata URL or XML, then click Read metadata. Or choose Enter manually.
- Click Save connection.
- Click Test sign-in to check what your provider sends. Nobody is signed in or created.
- Switch on Turn on single sign-on. People at your domains can now choose Continue with SSO on the sign-in page.
Single sign-on options
| Option | What it does |
|---|---|
| Require single sign-on | People at your domains can't use a password, an email link or Google |
| Owners can still sign in with a password | Keeps owners able to get in if the identity provider breaks |
| Create accounts on first sign-in | New people at your domain get an account and join automatically |
| Access for people who join this way | Their access, or the workspace default |
| Allow sign-in from your identity provider's app list | For the Vidler tile in Okta or My Apps. Off by default |
3. Set up SCIM provisioning
- Under User provisioning (SCIM), copy the SCIM base URL.
- Click Generate token, name it after your provider, and copy the token straight away. Vidler won't show it again.
- In your provider, use HTTP header (Bearer token) authentication with that URL and token. Open Set up Okta or Microsoft Entra ID for step-by-step settings.
- Under Groups, map each group your provider pushes to Admin, Creator, Lite seat or Viewer.
- Under When someone leaves, choose whether to deactivate or remove them, who receives their videos, and whether to End their sessions.
To stop a provider syncing, click Revoke next to its token, then Revoke token. People already provisioned stay as they are.