Skip to content

Identity for the workforce

One identity foundation for every organization.

Connect employees, contractors, business customers and partners with enterprise SSO, directory federation and organization-aware sign-in.

The situation

What this usually looks like

Three things we are describing, not three things we are offering. If two of them match the system you have, you are reading the right page.

  1. 01

    A person belongs to several organizations, and each one wants its own identity provider.

  2. 02

    Leavers keep access because deprovisioning never reached every downstream application.

  3. 03

    Every enterprise customer asks for SSO and each one becomes a bespoke integration.

The approach

How this is addressed.

What the platform does about the situation above, layer by layer, before any service names are involved.

Designed for real B2B complexity
A person may belong to several organizations, and every organization may use a different identity provider. ID Check Globe helps applications establish a reliable user identity and a clear organizational context at sign-in.
Let customers bring their identity provider
Support enterprise federation and organization-aware connection routing, so your business customers can use existing identity providers without each application requiring a custom integration.
Keep user lifecycle aligned
Connect directories and provisioning workflows, synchronize identities and manage joiner, mover and leaver events through standards-based interfaces.
Trusted identity, separate access policy
ID Check Globe authenticates the individual and establishes organization membership claims. What that authenticated principal is allowed to reach is determined by your application or a dedicated authorization layer.

The services involved

What this is built from.

A solution is a reading path through the catalogue, not a separate product. These are the services it draws on — each one with its own page, scope and integration detail.

Every service above establishes who or what is making a request. Deciding whether that authenticated principal may perform a particular action is authorization, and it stays with the consuming application or a separate authorization layer. Each service page states where it stops.

Identity for the workforce

Where this starts.

Create a development tenant and connect one application, or talk the architecture through first — tenancy, evidence, credential lifecycle, and which parts stay in your own stack.

Reading first is fine too: the developer portal covers APIs, SDKs and the standards each flow follows, and pricing sets out the packages and what is metered — the figures themselves are agreed with our team.