Answers to common questions about Single Sign-On (SSO) for Videri Portal. Videri supports SSO with any identity provider that can federate via SAML 2.0 or OIDC, including Okta, Azure AD / Microsoft Entra ID, Google Workspace, OneLogin, PingFederate, and ADFS.
What does SSO let our users do?
Once your organization is set up, your team signs in to Videri Portal with a single "Continue with SSO" button. They enter their work email, and are redirected to your organization's own identity provider login page to authenticate — no separate Videri password to remember or manage.
What identity providers do you support?
Any identity provider that supports SAML 2.0 or OIDC federation — this covers the large majority of enterprise identity providers, including Okta, Azure AD / Microsoft Entra ID, Google Workspace, OneLogin, PingFederate, and ADFS. If you use something else, ask your account team to confirm compatibility.
What do you need from us to set this up?
Which identity provider you use.
Whether your integration uses SAML 2.0 or OIDC.
The email domain(s) your employees use to sign in (e.g.
yourcompany.com).A contact on your identity provider admin team to exchange SAML/OIDC metadata.
Your target go-live date.
Your Videri account team will walk through these with you as part of setup. An intake form is available attached to the bottom of this article.
How long does setup take?
Setting up SSO involves a short configuration exchange between your identity provider admin and our engineering team, followed by testing before go-live. Your account team will confirm a timeline once they have the details above — it is not an instant, self-serve toggle today.
Will our existing users need to do anything?
No migration step is required. Once SSO is enabled for your organization, your users simply choose "Continue with SSO" at login instead of entering a Videri password.
Does enabling SSO turn off password login?
Not currently. SSO is additive — users can still sign in with a Videri password unless you've discussed a different requirement with your account team. If you need password login fully disabled for your organization, raise this with your account team as a specific requirement.
What happens when someone new joins our company?
Talk to your account team about how new users are added on your end today — this depends on your specific setup and isn't fully automatic for every organization yet.
Do you support automatic de-provisioning when someone leaves our company?
Not yet. Removing or disabling a user in your identity provider does not automatically remove their Videri access today. Please continue to notify your Videri account team directly when offboarding a user, in addition to your identity-provider-side offboarding.
We use more than one email domain — is that supported?
Yes. Let your account team know all the domains your employees sign in with, and we'll configure each one.
Can my employees' email domain accidentally be matched to another company's SSO configuration?
No. Each organization's SSO configuration is scoped specifically to the email domain(s) you provide us, and is not shared with or visible to any other Videri customer.
Who do I contact with questions?
Reach out to your Videri account team — they'll coordinate directly with our engineering team on your behalf.
Comments
0 comments
Article is closed for comments.