Newsroom/Product

Single sign-on with Entra ID, Google Workspace and Okta

Access to Kapālins follows the directory an organisation already runs, so joiners, movers and leavers are handled there, not by ticket.

At a glance
  • Sign in with Microsoft Entra ID, Google Workspace or Okta since 26 August 2026.
  • Identity-provider groups decide roles, and membership changes move roles automatically.
  • Deprovisioning a person in the directory disables their console sign-in.

What’s new

Since 26 August 2026 Kapālins has supported sign-in with Microsoft Entra ID, Google Workspace or Okta. SCIM 2.0 provisioning, which keeps users and groups in step with the directory, is available alongside it.

From 27 August an organisation’s identity-provider groups decide a person’s Kapālins role. When group membership changes, the role moves with it, and a role an administrator set by hand can be handed back to the directory.

Why it matters

Joiners, movers and leavers are handled in the identity provider rather than by ticket.

The same directories tell Kapālins about AI. OAuth grants in Entra and Okta are matched against 31 known AI apps, so an AI app someone connected with one click shows up in the inventory.

How it works

Users and groups come from the identity provider through SCIM 2.0. Deprovisioning a person in the directory disables their console sign-in, and groups become policy subjects.

Support access to a tenant is time-bound and needs a reason code. Every support session is logged and can be ended early.

Availability

Single sign-on reached production on 26 August 2026, and group-to-role mapping on 27 August.

Directory Provisioning (SCIM) is included in Fortress and is an add-on on Foundation and Growth.

Media contact[email protected]