Skip to main content
Settings → Auth & Security is where an organization connects OpenWork to its identity provider. It has two tabs:
  • Single sign-on (SSO): people sign in with your company account instead of a separate OpenWork password.
  • User provisioning (SCIM): people and groups are added to and removed from OpenWork when they change in your identity provider.
Older OpenWork versions, and organizations where Auth & Security is not turned on yet, show these as two separate pages: Settings → SSO and Settings → SCIM. Everything else on this page is the same. Links to the old pages open the matching Auth & Security tab.

Who can use it

On a plan without the feature, the tab says which plan includes it. People who can manage billing see Upgrade to Team (single sign-on) or Talk to us about Enterprise (user provisioning). See Pricing and licensing.

Single sign-on

Single sign-on works with any SAML or OIDC identity provider. Follow the guide for yours: Every connection goes through the same steps before anyone can use it:
  1. Open Settings → Auth & Security → Single sign-on (SSO) and save your identity provider’s details.
  2. Verify your email domain with a DNS TXT record.
  3. Run a real test sign-in.
  4. Turn SSO on.
Until all four are done, the connection stays off and people keep signing in the way they do today. Someone from your verified domain who signs in with SSO for the first time joins the organization as a Member. Once SSO is on, people at your verified domain see Continue with SSO first when they sign in. To make SSO the only way into your organization, turn on Require SSO (Enterprise plan). Depending on your organization’s settings, this switch is at the top of the Single sign-on (SSO) tab or under Authentication in Settings → General. Where available, Restrict this domain to our SSO also stops people at your domain from using a password or Google anywhere in OpenWork.

OIDC callback URLs

The OIDC callback is <callback-origin>/api/auth/sso/callback/<provider-id>. For the first connection, the provider ID is openwork-sso-<organization-id>. Find the organization ID in Settings → General. The callback origin is the server’s configured public API URL, or its authentication origin when no public API URL is configured. Ask your deployment administrator for the actual origin. Additional connections receive an ID when saved, so their callback cannot be derived from the organization ID alone. Use the saved connection’s Redirect URL as the authoritative value, including on deployments with separate web and API hosts.

Editing and recovery

An OIDC replacement save requires the client secret again, disables the connection, and resets its test state. Test the saved configuration before re-enabling it. The setup test uses a temporary session, not a normal SSO sign-in. Enforcement depends on deployment settings. Deployments without per-organization SSO enforcement require SSO as soon as it is enabled. Plan recovery before enabling or changing the only working connection. Disabling retains configuration but still requires authenticated management access. Deleting also removes linked provider-account data.

User provisioning

User provisioning (SCIM) keeps OpenWork in step with your identity provider: people you assign get access, and people you remove or deactivate lose it. You can also create OpenWork teams from your identity provider’s groups. User provisioning needs single sign-on turned on first. Then follow the guide for your identity provider: Google Workspace can be used for single sign-on but not for user provisioning; see Google Workspace SCIM provisioning. In Settings → Auth & Security → User provisioning (SCIM), create the connector, then give your identity provider the SCIM base URL and the bearer token shown once after you create or rotate it. Failed syncs are retried and listed on the same tab until they are resolved.