Sign-in and SSO
Provantix is an enterprise product, so identity is built around your organization's identity provider from day one.
Sign-in methods
- Email and password, for self-serve and early access.
- Continue with Google, managed by Provantix: nothing to set up. An admin adds the person, and the person signs in with their Google account. See below.
- Microsoft Entra ID (OIDC): sign in with your work account; the platform discovers your organization's Entra tenant from the email domain.
- Google Workspace (OIDC): sign in with your Workspace account, configured in Google Cloud Console by your administrator.
- Other OpenID Connect providers (Okta, Keycloak, Microsoft AD FS, Ping Identity, Auth0 and similar): choose Other OpenID Connect on the Single sign-on card and enter the provider's issuer URL. The provider must offer the authorization code flow, sign id tokens with RS256 and put the person's email address in the token.
SSO is available on every plan, including the entry tier, because a security product that charges extra for SSO is grading its own homework.
Restricting sign-in to your domain
The platform checks the signed-in identity against your organization's claimed domain:
- Entra: accounts from other tenants, including guest accounts, are rejected; only members of your tenant are accepted.
- Google: the Workspace hosted-domain (
hd) claim is checked, so consumer Gmail accounts are never accepted even if an account with that email exists.
A domain belongs to one organization: the first to set it up holds it, and a second organization is refused with "already routes this email domain". Claiming a domain does not let anyone in who is not on it, because the provider must vouch for each person as belonging to that domain. Provantix does not yet ask you to prove you own a domain with a DNS record, so set SSO up for your own domain before someone else does.
Continue with Google (managed by Provantix)
Provantix runs one Google sign-in for every organization, so no company creates an OAuth app or configures anything. It sits behind the same Continue with single sign-on button as an organization's own provider (below). With nothing typed in the email box, the button goes straight to Google: the person picks their Google account, and Provantix works out the rest.
One button, two kinds of single sign-on. What happens when someone presses Continue with single sign-on:
| What they typed | What happens |
|---|---|
| A work email whose organization has switched on its own single sign-on | They go to that organization's own provider. |
| A work email whose domain has no provider of its own, or no email at all | They go to Provantix's Google sign-in. |
| Either, but their organization has switched on its own provider and they came through Provantix's Google | They are refused with "your organization signs in with its own single sign-on. Enter your work email on the sign-in screen, then choose single sign-on". Provantix's Google is not a way around an organization's own sign-in. |
So a company such as workcrew.ai that has set up its own Google or Entra sign-in has its people type their email first; one that has not, such as a customer using only Provantix's Google, can press the button with nothing typed.
- The admin decides who may come in. An admin adds a person from Settings, Access tab, Members with a role, exactly as for a password invite. Google only proves who the person is. Someone no admin has added is turned away with "there is no Provantix account or invitation for this Google email yet", and no account is created for them.
- An invited person needs no link. Their invite is accepted when they first sign in with Google, and they get the role the admin chose.
- One account per person. If the person already has a Provantix account with a password, signing in with Google opens that same account; a second one is never created. This happens only when Google reports the email as verified. After the first Google sign-in, Provantix recognises the person by Google's stable id as well as by email.
- Several organizations. A person who belongs to more than one is asked which one to sign in to.
- Password sign-in still works alongside it.
Using your own identity provider (optional)
An organization that wants its own provider, for example Microsoft Entra ID with its own sign-in policies, can set it up on the Single sign-on card. Its people then choose Continue with single sign-on and type their work email first, because Provantix uses the domain to find that organization's provider. The rest of this section describes that.
Single sign-on with your own provider is configured per organization. Provantix does not run it for you: you create your own OAuth app and enter its details once. After that it covers everyone on the domain.
- In your identity provider, create an OAuth app. For Google Workspace, in Google Cloud Console set the OAuth consent screen to Internal (this keeps personal Google accounts out and needs no Google review), then create an OAuth client of type Web application. For Microsoft Entra ID, create an app registration in your tenant. Register the redirect address shown on the Single sign-on card,
https://app.provantix.tech/api/auth/sso/callback. - In Provantix, an organization admin opens Settings, Access tab, Single sign-on and enters the provider, the issuer (
https://accounts.google.comfor Google, fixed), the client ID, the client secret and the routing email domain, then switches it on.
The routing domain must be your own. It cannot be a Provantix staff domain, or one another organization already uses. A staff domain can be assigned to an owning organization by Provantix staff, and then only that organization can use it.
How a person signs in
On the sign-in screen the person types their work email, then chooses Continue with single sign-on. Provantix has to ask for the email first, because it uses the part after the @ to find which organization's identity provider to send them to. If no organization has SSO set up for that domain, the screen says single sign-on is not available for the address; it says the same whether the domain is unknown or SSO is switched off, so the page cannot be used to find out who is a customer.
Who is let in
By default SSO is invite-only. An admin invites people from Settings, Access tab, Members as usual. When an invited person signs in through the provider, Provantix matches them to their invite and gives them the invited role. A person who already belongs to the organization signs in normally. Anyone else on the domain is turned away with "your organization admin has not invited you", and no account is created for them.
An admin can switch off Only people an admin has invited can sign in with SSO on the same card. Then anyone the provider vouches for on the domain joins as a member the first time they sign in, with no invite.
Team access
An organization starts with its creator as admin. Admins invite colleagues from Settings, Access tab, Members:
- Invites are single-use, expiring, and attempt-limited.
- Accepting an invite signs the invited account into the inviting organization; accounts created via SSO never get a password set by an invite acceptance.
- With SSO on and invite-only left on, an invited person can also accept their invite simply by signing in through the identity provider.
Sessions
- Session tokens last 30 days and are held in memory only (never written to local storage); a full browser restart signs you out by design.
- Signing out deletes the session server-side.
- Changing your password revokes every existing session of the account.