# Enterprise SSO and directory sync, through your own WorkOS account

17 October 2026. Sell to companies whose IT team asks for single sign-on. Add the company as an enterprise, let its IT admin connect their identity provider from a link, require SSO if they ask, and let their directory add and block their people. It all runs through your own WorkOS account.

## Added

- **Authentication:** Enterprise single sign-on. Save your WorkOS API key on the new Enterprise tab under Authentication, add a company you sell to as an enterprise, and send its IT admin a setup link. They connect Okta, Microsoft Entra, Google Workspace or any SAML or OIDC provider in WorkOS's Admin Portal without asking you. Their people choose "Continue with SSO" on the hosted sign-in page and are sent to their own identity provider by the domain of their email. WorkOS bills the connections to your WorkOS account.
- **Authentication:** Require single sign-on per company. Once it is on, that company's people cannot sign in with a password, a magic link, a social account or a passkey: the sign-in page sends them to their identity provider instead. Sign-ins started from the identity provider's own dashboard land in your app too, once you set the sign-in endpoint in your WorkOS dashboard.
- **Workspaces:** Bind an enterprise to the workspaces its people belong in. Someone from that company who signs in for the first time lands in those workspaces with the role you set, without an invitation, and someone you later remove is not put back by signing in again.
- **Authentication:** Directory sync (SCIM). Turn provisioning on for an enterprise and its own directory adds and updates its people, puts them in the bound workspaces, gives them roles from their directory groups, and blocks and signs out the people who leave; someone rehired is let back in. Nobody the directory touches gets a welcome or "you were added" email. Changes arrive within five minutes, or within seconds with the optional webhook.
- **SDK:** A Single sign-on screen in the SDK's settings (from @buildbase/sdk 1.0.0). A workspace admin in your app sees which company the workspace belongs to, whether its single sign-on and directory sync work, and opens the setup for their IT admin, without asking you. Hide it, or keep it and drop the buttons, from the settings config.
- **Webhooks:** Three webhook events for the directory: enterprise.user_provisioned when it creates someone, enterprise.user_deprovisioned when it blocks someone, and enterprise.directory_synced once per enterprise per sync, with counts.
- **Authentication:** A warning before a company's SAML certificate expires. When it does, nobody at that company can sign in by SSO, and until now nothing said so. The enterprise's row and detail show "Certificate expires in 5 days" or "Certificate expired", with Check now and a link that opens the setup on the certificate for their IT admin. Two webhook events, enterprise.certificate_expiring and enterprise.certificate_renewed, let you page someone or email the customer.
- **Authentication:** Each enterprise has its own audit trail: sign-ins, refused sign-ins with the reason, people sent to SSO by the requirement, what the directory added, changed and removed, certificate warnings and every setup change. Read it in the enterprise's Activity section, filter it by kind and date, download it as CSV, or pull it with an API key for a SIEM. It reaches back as far as your plan keeps the auth audit log.
- **SDK:** The SDK's Single sign-on screen shows the certificate warning with a Renew button, and gives your customer's own admins their company's activity with a CSV download (from @buildbase/sdk 1.0.0), so their security team gets its sign-in report without a ticket to you.
- **Authentication:** An access policy for each company you sell to. Sign its people out after a stretch of inactivity (15 minutes to 30 days) or after a fixed time however active (1 hour to 180 days), allow sign-in and requests only from its own network (IPv4 or IPv6 ranges), and name up to five break-glass people who can still sign in, optionally only with a passkey, when its identity provider is down and single sign-on is required. Every break-glass sign-in is in the company's trail and sent as a webhook so someone can be paged.
- **Authentication:** Sign one of a company's people out, or all of them, at once: every session and every connected app or agent ends. From the people list or Sign everyone out in the console, or by the company's own admin in your app.
- **SDK:** The Single sign-on screen gives your customer's admins the same access policy and sign-out (from @buildbase/sdk 1.0.0). It offers the address they are saving from and refuses an allowlist that would shut them out; you can keep the policy to yourself in the console. Three new webhook events: enterprise.policy_updated, enterprise.break_glass_used and enterprise.sessions_revoked.
- **SDK:** Someone who opens your app from outside their company's allowed network keeps their session instead of being signed out, and your app hears about it once with useAccessRefused() or onAccessRefused, with a sentence ready to show. Back on the network, the app opens signed in.
- **Authentication:** Roles from your customer's identity provider, without provisioning. Map the roles WorkOS's role assignment sends at sign-in, or the identity provider's groups, to a role in your app or a workspace; they are worked out again at every sign-in, and saving the mappings applies them at once to everyone who has signed in.
- **Authentication:** You hear when a customer's IT admin deactivates, deletes or reactivates their single sign-on connection: three new webhook events (enterprise.connection_deactivated, _activated and _deleted), an entry in the company's activity, and a warning in the console while nobody can sign in through it.
- **Authentication:** Stream a company's audit trail to its own SIEM. Add up to three log streams per enterprise: an HTTPS endpoint (each request signed the same way as our webhooks), Datadog, or a Splunk HTTP Event Collector. Entries arrive in order within about ten seconds, and when the receiver is down nothing is lost: the stream retries for as long as it takes, says it is failing, and catches up once the receiver answers. Two new webhook events, enterprise.log_stream_failing and enterprise.log_stream_recovered, so you can page someone.
- **Authentication:** Insights for each enterprise: how many of its people signed in over the last 7, 30 or 90 days, how they signed in, who was refused and why, day by day, and the health of the connection, the certificate, the directory and each log stream.
- **Workflows:** Enterprise SSO events start workflows. A certificate about to expire, a connection your customer's IT admin turned off, a log stream that keeps failing, a break-glass sign-in and every other enterprise event are triggers under Enterprise SSO in the workflow builder, each with its details as merge fields, so you can email the customer's IT admin or page your own team without a webhook receiver of your own.
- **SDK:** Your customer's own admins get the same insights and manage their log streams from the Single sign-on screen, with a test event and the signing secret shown once (from @buildbase/sdk 1.0.0). If you keep their security settings yourself, they see the streams read-only.
- **Authentication:** Company admins, apart from workspace admins. Until now anyone who could edit a bound workspace's settings could change the whole company's access policy, read its trail or sign everyone out. Name the company's admins in the enterprise's detail, let the company name them from your app, or let its identity provider decide with a role mapping to Company admin; from then on only they manage the company's security settings. Two webhook events and workflow triggers, enterprise.admin_added and enterprise.admin_removed.
- **Authentication:** The company's trail now shows who joined, left or changed role in its workspaces: invitations sent and withdrawn, people added by hand, by single sign-on or by the directory, role changes and removals, with the workspace and who did it. Its admins read it, export it and stream it to their SIEM like the rest of the trail.
- **Authentication:** Connected apps and agents, for the company. See which third-party apps and AI agents a company's people have connected to their accounts, how many people and which scopes, and disconnect one person or everyone at once. The access policy decides which may connect at all: any, only the ones approved, or none. A refused app gets the company's sentence on the consent screen, and tightening the policy ends existing access at the app's next refresh. Signing people out, and the directory removing someone, now also take their connected apps' consents.
- **SDK:** Your customer's admins name their company admins and manage connected apps from the Single sign-on screen (from @buildbase/sdk 1.0.0), and the activity gains Workspace members, Company admins and Connected apps filters.
- **Authentication:** Company API keys. A company's own tools, its compliance archive, its SIEM jobs, the script that signs a leaver out, can now call your app as the company with a key that carries only the scopes it was given: read the trail, read people, sign people out, read or change the access policy, insights, company admins, connected apps and log streams. A key is shown once, can be limited to the company's addresses, lasts 30, 90 or 365 days or does not expire, and never manages other keys. Every change made with one is in the company's trail under the key's name.
- **Authentication:** Service accounts for each company. A company admin's own key stops working the moment they stop being an admin; a key that belongs to a service account outlives whoever set it up, so automation keeps running when people leave. Your team can make keys for a company's service accounts in the console, and revoke any key.
- **SDK:** Your customer's admins make and revoke API keys and service accounts from the Single sign-on screen, and see the key once beside the address it calls (from @buildbase/sdk 1.0.0).
- **Authentication:** Company roles. A company no longer has to make everyone who touches its settings an admin. Each person it names gets a role: Company admin manages everything, Security admin manages the access policy, sign-outs, connected apps, API keys, log streams and setup and only views the rest, and Auditor views everything and changes nothing. A company can make up to 20 roles of its own, area by area, such as a help desk that signs people out and reads the trail. Only a Company admin gives roles out, so no role a company makes can be used to climb to a broader one. A company API key someone makes for themselves can never do more than their roles allow, on the day it is made or after.
- **Workspaces:** Company groups. A company's admins put people in a group by hand, or link it to a group or role from their identity provider, and say what being in it gives: a role in up to 20 of the company's workspaces, and a company role. Someone added to the group joins those workspaces with that role, and someone who leaves it goes back to what they had before. It applies when the group is saved and again at every sign-in and directory sync, without your team writing a mapping.
- **SDK:** Your customer's admins manage their company's groups and roles from the Single sign-on screen, and each section of that screen shows only to the people whose role reaches it.
- **Webhooks:** Six webhook events and workflow triggers for the company's groups and roles: enterprise.group_created, enterprise.group_updated, enterprise.group_deleted, enterprise.role_created, enterprise.role_updated and enterprise.role_deleted. enterprise.admin_added and enterprise.admin_removed now carry the role given or taken away.
- **Authentication:** WorkOS verifies your customers' email domains. Add a domain to an enterprise and it goes on the company's WorkOS organization; its IT admin publishes the DNS record WorkOS's Admin Portal shows them, opened from Verify in WorkOS in the console or from the IT-admin invitation with its new Domain verification option. BuildBase keeps no DNS record of its own. A domain the IT admin adds and verifies in the portal shows up on its own, Refresh from WorkOS reads the verdict on the spot, removing a domain removes it in WorkOS too, and a domain counts only while WorkOS verifies it.
- **Authentication:** Joining by email domain. A company can let anyone with a verified email on its domains who signs in with a password, a magic link, a social account or a passkey become one of its people on the spot, or ask to join first, with requests its admins approve or decline. Someone declined is not asked about again for 30 days.
- **Authentication:** Claim the accounts already on a company's domains. The people at Acme who signed up with a password, and verified their email, before Acme became your customer are listed, and the company's admins or your team bring them in, 100 at a time, picked by hand or all of them: they join the company's workspaces and are signed out, so their next sign-in follows its policy and its SSO. Nobody is emailed; hook a workflow to enterprise.person_joined if you want them told.
- **Workspaces:** Rules for people outside the company in its workspaces, such as contractors. Allow them, limit them to editor or viewer and hold them to the company's IP allowlist, or block them: a blocked outsider cannot be invited or added, and one already in is refused and no longer sees the workspace. The workspace's owner is never refused or lowered.
- **Authentication:** Required single sign-on now reaches everyone on a company's verified domains, including accounts made before it was turned on, which link to the company at their first SSO sign-in. Break-glass still covers only the company's own people.
- **Authentication:** Someone who loses access to a company's setup, through a role, a group, a block, being signed out, leaving its workspace or removal from your console, has any WorkOS Admin Portal session they opened ended in WorkOS too.
- **Authentication:** The company API reads requests to join, the accounts on the company's domains and the people outside it, and approves, declines and claims, under people:read and people:write. GET / now answers each domain's status, who verified it and WorkOS's last error.
- **Webhooks:** Four webhook events and workflow triggers: enterprise.person_joined, enterprise.join_requested, enterprise.join_request_declined and enterprise.domain_removed; enterprise.domain_verified now fires on WorkOS's verdict. The WorkOS webhook you register from the console now carries the certificate, connection and domain events as well as the directory's, so they arrive in seconds; if you registered it earlier, choose Register again, and the endpoint it replaces is deleted in WorkOS for you.
- **Authentication:** Company audit logs in WorkOS, a switch on the Enterprise tab. Turn it on and each company's trail also goes to WorkOS: its IT team reads and exports it in WorkOS's Admin Portal, you choose how long WorkOS keeps it, from 30 days up to ten years, and its activity can stream to its SIEM from WorkOS. It is off by default because WorkOS bills it as an add-on to your own WorkOS account, and nothing changes until you turn it on. Retention can be raised but never lowered, so the console asks before it saves.
- **Authentication:** Two exports of a company's trail. The CSV stays for everyone and reaches back as far as your plan keeps the auth audit log. With company audit logs on, Export from WorkOS adds WorkOS's own: up to 31 days at a time from the last three months, as a link that works for ten minutes. Both are in the console, in your app and in the company API, and every download is now in the company's trail.
- **Authentication:** With company audit logs on, a company's new log stream comes from WorkOS: Datadog, Splunk, AWS S3, Google Cloud Storage, Microsoft Sentinel, Snowflake or any HTTPS endpoint. Your team sets it up from the console, or invites the company's IT admin to from there; each stream is billed to your WorkOS account, so the company sees its stream in your app but cannot start one. Streams BuildBase already sends for a company keep delivering until it deletes them, and every org without the switch keeps BuildBase's own.
- **SDK:** With company audit logs on, the Activity on the Single sign-on screen adds Export from WorkOS and Open the audit log viewer beside Download CSV, and Log streams shows the company's WorkOS stream, read only (from @buildbase/sdk 1.0.0).
- **Webhooks:** enterprise.log_stream_failing and enterprise.log_stream_recovered now say which kind of stream it was, source: buildbase or workos, so a workflow can tell a WorkOS stream in error from one of ours whose receiver stopped answering.
- **Authentication:** Roles WorkOS assigns, read for every company. When a company's IT admin assigns their groups to roles in WorkOS, BuildBase now reads the role WorkOS gives each person, from the directory as well as at sign-in, and offers it first in the enterprise's role mappings as WorkOS role. Map it to a role in your app, a workspace role or Company admin, or let the company link it to one of its groups. There is nothing to turn on, and your directory group, SSO role and SSO group mappings keep working beside it.
- **Authentication:** Let the IT admin assign roles in WorkOS, a switch per company in the console, off until you turn it on. The company's roles and groups can then be published to its WorkOS organization, and its IT admin assigns their identity provider's groups to them in WorkOS's Admin Portal, opened from Assign roles in WorkOS. Each role and group has a Show in the Admin Portal switch. What each role gives is still decided in BuildBase, WorkOS never takes away a role someone was named with by hand, and only your team can publish Company admin. A published role keeps its slug for as long as it stays published, so renaming it never breaks the IT admin's assignments.
- **Authentication:** A WorkOS roles card on each enterprise reads the company's roles back from WorkOS and says they are in sync, or what needs attention: a role deleted or renamed in the WorkOS dashboard, a change still waiting to be written, a role people carry that gives nothing. Each comes with its fix, such as Publish again, Retry now or Map it, and the enterprises list marks a company that needs a look. Taking out a role the IT admin still has groups assigned to is refused, with a sentence saying what to remove in the portal first.
- **Authentication:** The company API reads a company's roles in WorkOS at GET /workos-roles under admins:read, and its role and group changes take assignableInWorkOS to publish one or take it out.
- **SDK:** Once you turn it on for a company, its admins publish their roles and groups to WorkOS from the Single sign-on screen, see each one's slug and whether the company's roles are in sync, and open Assign roles in WorkOS for their IT admin (from @buildbase/sdk 1.0.0).
- **Webhooks:** enterprise.role_updated and enterprise.group_updated name workos among what changed when a role or group is published to WorkOS, renamed while published, or taken out, so a workflow can tell the company's IT admin a new role is ready to assign.
- **Authentication:** A company can keep its network to its own accounts. Its IT team sets their proxy to add an allowed-company-ids header naming the company to every request to your API host, and on that network a personal account, or another company's, is refused at sign-in and on every request, while the same session keeps working off that network. The header only applies in an app whose companies it names, so on the shared cloud host it never touches another app, and Check this network on the SDK's Single sign-on screen (from @buildbase/sdk 1.0.0) says what the proxy actually sent. Each refusal is in the company's trail with the refused account's email.
- **Authentication:** Every session your team opens as one of a company's people is now in that company's trail. A token exchange with an owner or admin key that names one of its people is recorded as Session opened by the app's team, with your key's name and the reason you send, and fires the enterprise.app_team_session webhook. In the company's access policy, Your team may sign in as the company's people (its admins see it as The app's team signing in as one of your people) can be set to Not allowed, from your console or by the company: the sessions your team has open as its people end, and the exchange is then refused with app_team_sessions_refused. Name your support keys for what they do: the company reads the name.
- **Authentication:** End one session on one device. Sessions, beside Sign out in a company's people list, shows each session a person has, with the device, browser, place, when it began and how they signed in, and End signs out a lost laptop while the person stays signed in everywhere else. It is in the console, on the SDK's Single sign-on screen (from @buildbase/sdk 1.0.0) and in the company API (GET and DELETE /people/:userId/sessions), and enterprise.sessions_revoked fires with scope: session.
- **Authentication:** People a company's policy signs out are told why. Instead of a bare 401, the next request gets session_ended with the reason and a sentence such as "Your company signs you out after 8 hours. Sign in again." Your app hears it with useSessionEnded or the onSessionEnded callback (from @buildbase/sdk 1.0.0), and the hosted sign-in page shows the same sentence when they come back.

Source: https://www.buildbase.app/changelog/enterprise-sso-and-directory-sync
