Skip to main content
VirtualInterview.ai
Docs menu

SSO and SCIM provisioning

Verify your email domain, then connect your identity provider over SAML 2.0 so your team signs in with single sign-on. To create, update and deactivate portal users from the identity provider, generate a SCIM token and point the provider at the SCIM 2.0 base URL. Both live under Settings, then Security.

How-to · Last checked against the product on

Before you start

You need the Manage Integrations & API Keys permission, which Owners and Admins have by default; without it the Security tab is hidden. You also need access to your domain’s DNS and admin access to your identity provider.

Verify a domain

  1. Go to Settings → Security. Under Verified domains, enter the domain and select Add domain.
  2. Publish the TXT record shown at your DNS provider. The domain shows Pending verification until then.
  3. Select Verify now.

Each verified domain has Auto-join on hiring sign-in, off by default. Set it to Member (no portal), Manager or Admin to add people from that domain to the workspace with that role when they sign in.

Set up single sign-on

  1. Under Single sign-on (SAML 2.0), copy the service provider details (Entity, ACS and Metadata) into a new SAML application in your identity provider. Use a persistent or email-address NameID, and send the email address and display name claims.
  2. Paste your identity provider’s Metadata URL, or tick Paste XML instead of a URL and paste the Metadata XML.
  3. Select Save connection. At least one verified domain is needed before the connection can go live.
  4. Use Test connection, then Enable.

Your team then signs in on the hiring portal’s sign-in page with Continue with SSO. Once the connection is active, two options apply:

Sign-in options
OptionEffect
Require SSO for verified domainsPassword sign-in is refused for anyone whose email is on a verified domain.
Keep a password path for organisation adminsBreak-glass access, so a misconfigured identity provider cannot lock out the people who can fix it.

Provision users with SCIM 2.0

  1. Under User provisioning (SCIM 2.0), copy the Base URL.
  2. Name a token and select Generate token. Copy it straight away: it is shown once.
  3. In your identity provider’s SCIM settings, enter the base URL and paste the token as the bearer token.

Group names decide the role: a group whose name contains “admin” grants Admin, “manager” grants Manager, and everyone else is a Member. Deactivating a user in your identity provider removes their access at once. Provisioned users appear in the same card, marked Active or Deactivated, and Not signed in yet until they first sign in.

What the SCIM endpoint supports

SCIM 2.0 resources
PathMethods
/UsersGET (list, with filter), POST
/Users/{id}GET, PUT, PATCH, DELETE
/GroupsGET, POST
/Groups/{id}GET, PUT, PATCH, DELETE
/ServiceProviderConfigGET
/ResourceTypesGET: the User and Group resource types
/SchemasGET

Authentication is a per-workspace bearer token. PATCH and filtering are supported; bulk operations, sorting, ETags and password changes are not. A user filter matches one attribute exactly:

Filter
GET /Users?filter=userName eq "ana@example.com"

You can filter on userName, externalId or emails.

Was this page clear?