Skip to content
All changes

Stricter rules for one of a company's workspaces

A company you sell to can now hold one of its workspaces to stricter rules than its own access policy, never looser, and its people confirm it's them there instead of being signed out everywhere.

Added
3
  • AuthenticationStricter rules for one workspace. A company you sell to can hold one of its bound workspaces, say its finance workspace, to shorter sessions, only its office network, fewer ways in or single sign-on required, fewer agents, people outside it kept out, or your team not signing in as its people there. Its admins set them on the Single sign-on screen in your app (from @buildbase/sdk 1.0.0), your team in the console, and its scripts with a company API key. A workspace's rules are never looser than the company's own policy, which still applies first: anything looser is refused and says which rule and why.
  • AuthenticationSomeone a workspace's rules refuse is asked to confirm it's them there, with single sign-on or their passkey, and keeps working in the company's other workspaces with the same session; nobody is signed out when the rules change. Single sign-on is offered only when the app they signed in to offers it, and someone with no way to confirm is asked to sign in again instead. The refusal is a 403 your app can show as it is, and the SDK's new useWorkspaceAccess and WorkspaceAccessRefused offer Confirm it's you or Sign in again to match. Notifications from that workspace stay out of their inbox, and its live updates are not sent, until they are back in.
  • WebhooksA new event, enterprise.workspace_policy_updated, says when a company sets, changes or removes a workspace's rules, or loses them with the workspace's binding, and a matching workflow trigger, Workspace Policy Updated, starts a workflow from it.

Use what shipped this week

Everything in this release is already in the console and the SDK.

Free plan7-day free trial on paid plansNo credit card required