Organization Users

Single Sign-On (SSO)

Single sign-on lets your people sign in to TestInvite with their company account through SAML 2.0 or OpenID Connect; you set it up yourself in five steps and prove it works with Test SSO before anyone depends on it.

Updated 2026/11/12

Single sign-on (SSO) lets your employees sign in to TestInvite with the same company account they use for email — no separate TestInvite password. Your company's identity provider (Microsoft Entra ID, ADFS, Okta, Google Workspace, Keycloak or any other SAML 2.0 / OpenID Connect provider) checks who they are; TestInvite trusts its signed answer.

What you get

  • One account, one password — people sign in the way they already do, including multi-factor authentication and Windows sign-in.
  • Central control — who may use TestInvite is decided in your identity provider; when someone leaves, disabling them there stops their SSO sign-in.
  • Automatic user creation (optional) — new colleagues get a TestInvite user at their first sign-in, in the folder, group and role you choose.
  • Enforcement (optional) — require SSO for your company's email domains, while the organization owner always keeps password access.
  • Self-service and safe — you configure everything yourself and run a built-in Test SSO before turning it on.

Who does what

TestInvite organization ownerIdentity provider administrator (IT)
WhereTestInvite: Organization → Configure → Sign-in & Security → edit → Single Sign-OnYour identity provider's admin console
DoesChooses the protocol, shares TestInvite's values, enters the identity provider's values, sets domains and user rules, runs Test SSO, turns SSO onRegisters TestInvite as an application, configures which email/name to send, assigns users, shares the identity provider's metadata or client credentials
NeedsOwner access to the TestInvite organizationThis guide and your TestInvite organization ID

Your IT team can do their part from this documentation and your organization ID alone: every TestInvite value is built from it (see SSO Settings Reference). The owner finds the organization ID in the info menu next to the title of the Organization page.

Before you start

☐
You are signed in as the organization owner.
☐
Unique emails is turned on (Sign-in & Security → User Management). TestInvite matches people by email, so one email must belong to one person.
☐
You know your company's email domains (for example company.com).
☐
You have a contact who administers your identity provider.

Five steps to SSO

  1. Understand — new to SSO? Read How SSO Works (10 minutes). Then pick a protocol: SAML or OIDC.
  2. Configure your identity provider — follow the guide for yours: Microsoft Entra ID, ADFS, Okta, Google Workspace, Keycloak, or any other identity provider.
  3. Configure TestInvite — enter the identity provider's values, your domains and user rules. Every field: SSO Settings Reference.
  4. Test — click Test SSO and sign in once: Testing Your SSO Connection.
  5. Go live — turn SSO on as Optional, pilot, then Required: Going Live with SSO.
Nothing changes for your users until you turn SSO on and click Save. You can test as often as you like before that.

Your TestInvite values at a glance

Replace <ORG-ID> with your organization ID. The same values, ready to copy, are on the SSO settings screen.

ValueURL
SAML Entity ID and metadata URLhttps://www.testinvite.com/api/v1/auth/sso/<ORG-ID>/saml/metadata
SAML ACS URL (Reply URL)https://www.testinvite.com/api/v1/auth/sso/<ORG-ID>/saml/acs
OIDC Redirect URIhttps://www.testinvite.com/api/v1/auth/sso/<ORG-ID>/oidc/callback
Sign-in URL (bookmarks, app tiles)https://www.testinvite.com/api/v1/auth/sso/<ORG-ID>/initiate

When something goes wrong

Every failure has an error code with its own fix in SSO Troubleshooting. Common questions: SSO FAQ.

In single sign-on your identity provider proves who the user is with a signed message, and TestInvite checks that message before letting the user in — no TestInvite password is involved.

SAML and OIDC give users the same sign-in and the same security in TestInvite; the practical difference is that OIDC needs your identity provider's token endpoint to be reachable from the internet, while SAML does not.

Every SSO setting explained: what it is, what it enables, an example, and what happens when it is wrong — from the protocol and identity provider values to domains, enforcement, attribute mapping and automatic user creation.

With ADFS, TestInvite is added as a relying party trust (SAML) or an application group (OpenID Connect), and a claim rule must send the user's email — as an attribute and, for SAML, as the Name ID.

In Entra ID, TestInvite is an enterprise application (SAML) or an app registration (OpenID Connect); for SAML the App Federation Metadata URL is all TestInvite needs, and users must be assigned to the application.

In Okta, TestInvite is an app integration (SAML 2.0 or OIDC web application); for SAML, Okta's metadata URL fills in TestInvite in one step, and people must be assigned to the app.

Google Workspace connects to TestInvite as a custom SAML app; Google offers its metadata as a file to download, so it is uploaded to TestInvite rather than imported from a URL.

In Keycloak, TestInvite is a client in your realm: import TestInvite's SAML metadata to create a SAML client, or create an OpenID Connect client with client authentication on.

Any identity provider that speaks standard SAML 2.0 or OpenID Connect works with TestInvite; this page lists exactly what TestInvite sends, what it expects back, and which values go where.

Test SSO runs a real sign-in against unsaved settings and reports every check, the attributes received and the user it would resolve to — without signing anyone in, creating users or changing anything; SSO can only be turned on after a passed test.

A safe SSO rollout turns SSO on as Optional first, lets a pilot group sign in, and only then switches to Required — while the organization owner account keeps password sign-in as a way back in.

Every failed SSO sign-in carries an error code; each code has a section here with what it means, its usual causes and the exact fix — and Test SSO shows the failing check and every attribute the identity provider sent.

Short, direct answers about TestInvite SSO: lockout protection, leavers, MFA, candidates, several domains, certificate expiry, and what TestInvite stores.