Skip to main content
Single sign-on (SSO) lets people sign in to Variable with the account they already use at work. Your identity provider (IdP) — the system that holds your company’s user accounts — vouches for who they are, so nobody needs a separate Variable password, and disabling someone in your IdP stops them signing in through SSO. Variable connects to your IdP over OpenID Connect (OIDC), an identity layer built on OAuth 2.0. We support two providers:
  • Microsoft Entra ID, formerly Azure Active Directory (Azure AD)
  • Google Workspace
SSO is available on enterprise plans.
These guides use the redirect address of the hosted app. If you run Variable yourself, register your own address instead and configure OAuth through the environment variables in Self-hosted.

How setup works

You create an app in your IdP and send us its credentials; we set up the connection on our side. SSO is not something you switch on in the app.
1

Verify your email domain in Variable

SSO is tied to the email domains you own, and only a verified domain can be linked. Follow Verify your domain below.
2

Create the app in your IdP

Follow the guide for Microsoft Entra ID or Google Workspace. It ends with a client ID and a client secret.
3

Send us the credentials

Through an agreed-upon secure channel, send us the provider, the client ID and client secret, the domains to cover (for Microsoft, also your tenant ID), and a contact who can test the sign-in.
4

Invite your team

SSO proves who someone is, but it does not by itself add them to your account. See Give people access.
5

Test the sign-in

We confirm when the connection is live. Keep an owner signed in until a second person has signed in through SSO.

Verify your domain

You need the admin role to verify a domain.
  1. Go to Settings → Company and find the Domains card.
  2. Select Add Domain, enter your domain, for example acme.com, and select [Verify Domain] next to it.
  3. Add the DNS TXT record shown: name it _variable-domain-verify on your domain, with the value Variable gives you. DNS changes can take up to 72 hours to propagate.
  4. Select Check now. The domain shows Verified once the record is found.
Leave the TXT record in place. Variable re-checks it, and Microsoft sign-ins stop for a domain that is no longer verified. Domains are matched exactly. acme.com does not cover eu.acme.com, so verify and link every domain your people sign in with, and list them all when you contact us. For Google Workspace, also include your primary Workspace domain, even if nobody signs in with it: Google reports it for every account in your organization.

Give people access

Signing in through your IdP does not by itself give anyone access to your Variable account. Either invite people before they sign in, or switch on Auto-join for your domain. To invite someone:
  1. Go to Settings → Users and select Invite.
  2. Enter the same email address they use at work, and assign a role.
To let everyone on your domain in, go to Settings → Company, find the Domains card, and switch on Auto-join for the verified domain. Someone who then signs in through SSO with an address on that domain, and who doesn’t belong to a company yet, joins your account as a Contributor. If you run Variable yourself with its built-in password sign-in, Auto-join also applies to people who sign up with an email and password: they join when they open their verification link. If they open it in a browser where they aren’t signed in, Variable asks them to sign in first. If they’re signed in as someone else, Variable asks them to Sign out, then sign in to their own account to finish verifying. Auto-join stops when your account has no seats left; invite people again once you add seats. Someone who signs in with neither an invitation nor Auto-join is not added to your account. Instead, Variable asks them to set up a new company account of their own. If that happens, sign them out, invite them or switch on Auto-join, and have them sign in again.

Keep it working

  • Client secret expiry. Microsoft client secrets expire, at most 24 months after they are created. When one does, nobody at your company can sign in through SSO. Create a new secret before the old one lapses and send it to us through an agreed-upon secure channel.
  • Keep a way in. Make sure at least one owner has confirmed they can sign in through SSO before you rely on it.
  • Offboarding. Disabling a person in your IdP stops new SSO sign-ins, and a session they have open can stay active until it expires. To end someone’s access immediately, also remove them from Settings → Users in Variable.

Troubleshooting

Contact us through your agreed channel with the time of the attempt and the email address used.