Platform

Your directory, our door.

SAML and OIDC with setup guides for Okta, Entra, Google, and GitHub; SCIM provisioning; group-to-role mappings; and MFA you can enforce per workspace. Staff auth stops being a spreadsheet.

Explore highlights

Sound familiar?

Password policy per client

Enterprise buyers bring their own rules, and their own IdP. SAML and OIDC connections let the directory be the policy.

Manual provisioning

Creating accounts by hand, removing them by memory. SCIM keeps workspace membership in lockstep with your directory.

MFA by suggestion

Optional second factors protect nobody. Per-workspace enforcement makes staff MFA a policy, not a preference.

Enterprise identity, first-class

01SAML & OIDCWorkspace-scoped connections with ACS and metadata helpers, IdP metadata upload, and guides for the big four providers.
02SCIM 2.0 provisioningUsers and groups flow from your directory; tokens rotate from the admin when you need them to.
03Group-to-role mappingsIdP groups and claims map onto workspace roles. Access follows the org chart automatically.
04Enforceable MFATOTP, email, and SMS factors for staff, with a workspace switch that makes them mandatory.
05Buyers and staff, separatedStorefront social login and staff SSO are different bindings on purpose. One can't impersonate the other.
06Local when you want itPassword auth stays available per workspace, enterprise when you need it, simple when you don't.

Connecting your directory

  1. 01Add the connectionSAML or OIDC, with the setup guide for your provider beside the form.
  2. 02Map the rolesPoint IdP groups at workspace roles once.
  3. 03Turn on SCIMProvision and deprovision from your directory, automatically.
  4. 04Enforce MFAFlip the workspace policy; staff enroll on next sign-in.

Wire up your IdP

SAML, OIDC, SCIM, and MFA, in the demo workspace.