Authentication settings overview

How the Domains, Single sign-on, SCIM provisioning, and Local accounts cards work together, what the plan requires, how to verify a domain, and what forcing single sign-on does.

Written for
admin
Roles
owner, admin
Requires
Owner or Admin; Business plan or higher to set anything up (not the trial); Browser session with a recent re-authentication
Feature
authentication

By default everyone logs in to SAQ with a password or a passkey, owners and admins add an authenticator code, and regular client users get a magic link. Settings → People → Authentication is where a workspace adds enterprise sign-on on top: verified domains, one OpenID Connect connection, and SCIM provisioning. The page has four cards, set up in that order. A card whose step is not available yet is dimmed, everything in it is disabled, and a notice at its top says what it needs; the notice disappears, and the card wakes up, as soon as the earlier step is done. This page explains how they fit together; the connection and SCIM each have their own page.

Before you start

  • You need the Owner or Admin role. Every change here asks you to confirm your identity.
  • Setting anything up requires the Business plan or higher; the trial does not include it. On the trial and on Team the cards stay visible but their forms are disabled and dimmed, under the note "Available on the Business plan and higher. What is already set up keeps working and can be turned off or removed; nothing new can be added on the current plan." An active connection keeps logging people in after a downgrade, and SCIM can still deactivate users but not create them.
  • SAQ supports OpenID Connect only. There is no SAML.

The four cards

Card What it does Available when
Domains Proves by DNS that the workspace controls a domain. Always.
Single sign-on (OIDC) One connection to an identity provider. Logs in people whose address is on a verified domain, or who are already linked. A domain is Verified. Until then the card reads "Verify a domain first. The connection signs in only addresses on a verified domain, so it has nothing to do until a domain above is Verified."
Force SSO The switch on each domain row that makes single sign-on the only way in for that domain. The domain is Verified, the connection is Active, and your own session came through it. A note under the domain table says which of these is still missing.
SCIM provisioning Lets the identity provider create, update, and deactivate workspace users. A domain is Verified: SCIM only provisions addresses on one. Until then the card reads "Verify a domain first. SCIM provisions only addresses on a verified domain."
Local accounts Shows who can still use a password or passkey here. Always; it sums up which domains are forced to single sign-on.

A card that already has something set up is never gated, so a connection or SCIM tokens created earlier can always be turned off or removed even if the domain they relied on has since been removed.

Verify a domain

  1. Under Domains, enter the domain and select Add. The domain is the part after the @ in your users' email addresses (for anna@acme.example it is acme.example), not the workspace's website: forcing single sign-on later applies to everyone whose address is on it.
  2. Publish the TXT record the card shows at your DNS provider: name _saq.<domain>, value saq-verify=<token>. The token is specific to this workspace and domain.
  3. Select Verify now. The status moves from Pending to Verified; if the record is not found yet, the card says why under "Not verified yet".

Verified domains are re-checked weekly, and a record published later is picked up on its own. If the record disappears, the domain keeps its status for a 7-day grace period: the card shows "The record has not resolved since {date}. Force SSO is turned off after 7 days.", the owners receive an email, and the check runs daily. When the grace period runs out, Force SSO is turned off for the domain, the domain is marked Failed, and the owners are told again. Restore the record and select Verify now to recover. Two workspaces can each verify the same domain.

Removing a domain turns Force SSO off for it first; members keep their accounts.

Force single sign-on

Force SSO is a per-domain toggle switch on the Domains card, labelled On or Off; moving it opens a confirmation before anything changes. It requires a Verified domain and an Active connection; until the connection is Active the switch is inert, and a note under the table says what is still missing ("Force SSO becomes available once a domain is Verified and the single sign-on connection below is Active", then "…once the single sign-on connection below is Active and your own session came through it", then "To force SSO, log out and log in with this workspace's single sign-on first, so that nobody, including you, is locked out"). To turn it on, your own session must have come through this workspace's single sign-on, and you confirm your identity. The confirmation names how many current members are on the domain.

Forcing applies to the people whose email address is on that domain, and only to them. An owner whose address is on another domain, verified or not, is not affected by the switch; forced SSO is not a workspace-wide setting.

From that moment, for people whose address is on the domain:

  • Only a session that came through the connection can enter this workspace. Password and passkey sessions are locked out of the workspace and sent to the identity provider; a password session is never upgraded silently.
  • Their personal API tokens are revoked, and creating a new one requires a session that came through single sign-on.
  • The login page sends their address straight to the identity provider.

Forced SSO is a property of this workspace, not of the person: the same account can still use a password in another workspace that does not force the domain. Turning it off, removing a domain, or deactivating or removing the connection needs an owner or admin with a recent re-authentication of any kind, not an SSO session, so the way back never depends on the provider. If the provider becomes unreachable, the connection is marked Error and forced SSO is inert until an admin tests it again. See Set up single sign-on.

Local accounts

The Local accounts card sums up the result: "Password and passkey login are available to everyone whose domain is not forced to single sign-on." It lists the forced domains, if any, and the number of workspace users. Exemptions from forced SSO (break-glass accounts) do not exist yet.

Two-factor authentication

Owners and admins must have two-factor authentication (an authenticator app or a passkey) to enter a workspace; members and client users are encouraged but not required. Single sign-on can satisfy this when the connection has an MFA assurance rule the identity provider's token meets (for Microsoft Entra ID, amr contains mfa, which requires the amr optional claim in the app registration's manifest; see Set up single sign-on). Otherwise owners and admins finish with their local authenticator code after the identity-provider round trip. The assurance counts only in the workspace whose rule was met.

Common problems

The cards are locked. The plan does not include single sign-on. An owner can change it under Settings → Organization.

"Verify a domain first." The single sign-on and SCIM cards are dimmed until a domain is Verified; Force SSO needs one too.

I set up single sign-on and can still log in with my password. Three things are needed before a password is refused, and each is visible on the page: the domain row's Force SSO switch is On, the connection is Active, and your own address is on that domain. Even then, the password login itself succeeds; it is entering the workspace that is refused and redirected to the identity provider, so a person can still reach Account and other workspaces. See Force single sign-on.

"Log in through this workspace's single sign-on before making it required." Log out, log in with Continue with {workspace} SSO, and try again.

"The verification record is missing. Restore it before making sign-on required." The domain is in its grace period. Republish the TXT record and select Verify now.

Everyone is locked out because the identity provider is down. After three failed round trips in fifteen minutes the connection is marked Error and forced SSO stops applying, so owners and admins can log in with a password to fix it.