The Identity Journey

An interactive walkthrough of how identity flows through your organization

01 / 06

Meet the Identity Providers

Google Cloud Identity Microsoft Entra ID Others Okta · JumpCloud · OneLogin ⇅ INTERCHANGEABLE VIA OPEN STANDARDS ⇅ Your Identity Provider the single source of truth for every account, group & policy SAML 2.0authentication OIDCauthentication OAuth 2.0delegated authz SCIMprovisioning Every connected app speaks one or more of these four protocols back to the IdP.

Whichever provider you choose, it stores and manages:

display name email department groups security policies account status
02 / 06

Single Sign-On: one login, every app

SAML 2.0
OIDC
Browser App (SP) IdP 1click “Sign in with SSO” 2302 redirect + AuthnRequest 3browser forwards the AuthnRequest to the IdP authenticate (MFA / existing session) 4signed SAML assertion (XML) — your identity, sealed 5POST assertion → ACS endpoint validate signature → session granted ✓
Format
XML
Since
2005
Best for
Enterprise SSO
Transport
Browser redirect only
Browser App (RP) IdP 1click “Sign in with SSO” 2302 → authorize?scope=openid 3authorization request reaches the IdP authenticate + consent to scopes 4302 ← one-time authorization code 5code → app callback URL 6back-channel: code ⇆ ID token (JWT)server-to-server — the browser never sees the token read claims → session granted ✓
Format
JSON / JWT
Since
2014
Best for
Modern & mobile apps
Built on
OAuth 2.0
03 / 06

Your connected world

Every app trusts one hub. Click an app to see what identity data flows through.

Your IdP one login · one policy Slack SAML Salesforce SAML GitHub SAML Zoom OIDC Jira SAML AWS SAML
Click any app above to see the identity data it receives.
How SCIM automates user lifecycle across each app:
Slack
CreateUpdateDeactivateGroups
Business+
Salesforce
CreateUpdateDeactivateProfiles
Enterprise
GitHub
CreateUpdateDeactivateTeams
Ent. Cloud
Zoom
CreateUpdateDeactivateGroups
Business
Jira
CreateUpdateDeactivateGroups
Guard
AWS
CreateUpdateDeactivateRoles
IAM IdC

Yellow = partial or non-standard · Plan = minimum required for SCIM

04 / 06

SCIM: the automation layer

HR systemthe trigger Your IdPsource of truth SCIM 2.0 — REST + JSON POST PATCH DELETE / active:false Slack GitHub AWS … and every other connected app

SCIM (System for Cross-domain Identity Management) is a REST API standard that automates user lifecycle management. Instead of manually creating and removing accounts, your IdP pushes changes automatically.

CREATE
New hire added to HR system. SCIM provisions accounts across all connected apps within minutes. No IT tickets needed.
UPDATE
Employee changes department or role. SCIM updates group memberships, permissions, and attributes across every app simultaneously.
DEACTIVATE
Employee departs. SCIM suspends or removes their accounts from all connected apps instantly. No orphaned access.
05 / 06

The offboarding question

An employee's last day. Their access to company data across every connected app must be revoked. How does your organization handle it?

With SCIMone HR event all access revoked in minutes · sessions killed · audit logged Manualticket per app 7+ days — forgotten apps, shared accounts & API keys keep access
With automation
  • HR marks departure in system
  • IdP triggers SCIM deprovisioning
  • All app access revoked in minutes
  • Sessions terminated automatically
  • Audit trail generated
With SCIM-based automation, the entire offboarding process is triggered by a single action in your HR system. The IdP propagates the status change to every connected application via SCIM DELETE or PATCH requests. Active sessions are invalidated, OAuth tokens are revoked, and a complete audit trail is generated for compliance. Average time to full deprovisioning: under 15 minutes.
Without automation
  • IT creates ticket for each app
  • Manual login to each admin console
  • Some apps forgotten or delayed
  • Shared accounts overlooked
  • No centralized audit trail
Without automation, IT must manually disable accounts in each application individually. The average organization takes 7+ days to fully deprovision a departing employee. During that window, the former employee retains access to sensitive data, creating security risks. Shared credentials, API keys, and service accounts are frequently overlooked, leaving persistent access long after departure.
The individual perspective: You authenticate once and access everything. The admin perspective: Every connected app is another account to manage, another access point to secure, and another system to deprovision when someone leaves. Identity lifecycle management is the bridge between convenience and security.
Google vs Microsoft: SCIM provisioning capabilities
Google Workspace
Outbound SCIMAuto-provisioning limited to ~30 Google Workspace Marketplace apps. No native SCIM client for arbitrary endpoints.
Custom AppsRequires Cloud Identity Premium ($7.20/user/mo) or a third-party IdP like Okta for SCIM to non-Marketplace apps.
Group SyncManaged via Google Groups API, separate from SCIM user provisioning. Limited cross-app group mapping.
Attribute MappingMinimal customization. Fixed attribute set per auto-provisioned app.
DeprovisioningSuspends Google account. App-level deprovisioning depends on each integration's implementation.
Best ForGoogle-ecosystem orgs, startups primarily using Marketplace-integrated apps.
Microsoft Entra ID
Outbound SCIMBuilt-in SCIM 2.0 client provisioning to 100+ gallery apps and any custom SCIM endpoint.
Custom AppsFull support for non-gallery apps via custom SCIM connector. No additional licensing for provisioning.
Group SyncScope-based provisioning — assign specific Entra ID groups to each app. Supports group-to-role mapping.
Attribute MappingRich expression language with transformations, functions, and conditional logic per app.
DeprovisioningSupports soft-delete (PATCH active=false) and hard-delete. Quarantine mode pauses on high error rates.
Best ForDiverse SaaS environments, enterprises needing fine-grained provisioning control and audit trails.
06 / 06

Your identity architecture

Google Microsoft Okta · JumpCloud Your IdPone identity · everywhere SAML 2.0 OIDC OAuth 2.0 SCIM your connected world — authenticated, provisioned, governed

One source of truth

Your IdP centralizes identity. Every app trusts it for authentication, so you never manage separate passwords.

Protocols matter

SAML and OIDC both achieve SSO but differ in format and era. Understanding both helps you evaluate vendor support.

Automation is essential

SCIM turns manual IT work into automated workflows. Provisioning, updates, and offboarding happen in minutes, not days.

Offboarding is security

Every unrevoked account is a risk. Automated deprovisioning closes the gap between departure and access removal.