Single sign-on
Let people sign in through your company's identity provider over SAML, with Okta, Microsoft Entra ID or Google Workspace.
With single sign-on, people at your company sign in to VariantGate through your own identity provider, such as Okta, Microsoft Entra ID or Google Workspace, over SAML 2.0. Whoever your provider lets in can sign in; whoever it stops cannot. Single sign-on is part of the Enterprise plan.
Getting it set up
- In your identity provider, add VariantGate as a SAML application with the details below.
- Email support@variantgate.com with the application’s metadata URL and every email domain your people sign in with, such as
acme.com. - We add your provider and confirm. From then on, anyone with an email at those domains can choose Sign in with SSO.
The metadata URL must start with https://, and the domains must be ones your company owns.
What your identity provider needs
- Entity ID
- https://auth.variantgate.com/auth/v1/sso/saml/metadata
- Metadata URL
- https://auth.variantgate.com/auth/v1/sso/saml/metadata
- Reply (ACS) URL
- https://auth.variantgate.com/auth/v1/sso/saml/acs
- Name ID format
- Email address
- Attribute
- email: the person's work email
Signing in
- On the sign-in page, choose Sign in with SSO.
- Enter your work email. Only the part after the @ is used.
- You are sent to your company’s sign-in, then back to the inbox.
If nobody has set up single sign-on for your domain, the page says so; an emailed sign-in link still works.
Accounts and workspaces
- Single sign-on decides who can sign in, not which workspace they see. An owner still invites people under People, and chooses their role.
- An account made through single sign-on is separate from one made with an emailed link, even for the same address. Someone who used VariantGate before needs a new invitation after switching.
When someone leaves, remove them in your identity provider so they cannot sign in again, and under People so they lose the workspace at once.
Running VariantGate yourself
On your own server you add identity providers yourself. See Self-hosting.