Automate user lifecycle management with a SCIM 2.0 connector designed for tenant-scoped operation and a detailed audit history. See the capability matrix on the features page for what is supported today.
How provisioning flows · illustrative
Illustrative diagram — not a live feed; no customer data shown.
Access your area
Platform Administrator
Full platform control. Manage tenants, configure SCIM clients, monitor jobs, and review audit events across the entire deployment.
Tenant Operator
Manage your tenant identity synchronization. Configure attribute mappings, trigger sync jobs, and monitor connector health in real time.
End Customer
Access your provisioning status, manage your account, and view users and groups synced to your organization via SCIM.
A focused SCIM 2.0 connector with a published capability matrix — designed for any SCIM 2.0-capable identity provider — Okta, Microsoft Entra ID, Google, OneLogin, Ping, or custom/in-house. See the capability scope for the current supported subset.
Bearer-token authentication, hashed at rest, scoped per tenant. Rotate and revoke at any time. No SAML or OIDC sign-in today — see capability matrix.
Structured, tenant-scoped audit events for every SCIM operation and operator action. Supports security reviews and customer audits with detailed provisioning logs.
Strict tenant isolation at the data and runtime layers. Tokens, queries, and audit streams scoped per tenant. Operator and customer surfaces use separate auth stacks.
Standards-aligned SCIM 2.0 endpoints (Users, Groups, ServiceProviderConfig, Schemas, ResourceTypes). Narrow filter subset and PATCH-based updates — see capability matrix for the current scope.
Distinct authentication stacks for platform operators, customer portal users, and SCIM clients. Coarse scim:read and scim:write scopes for the data plane today; finer-grained authorization is on the backlog.
Your identity provider pushes SCIM requests to LabsNinja as users are created, updated, or deactivated. Provisioning state is visible in the customer portal and the audit log.
The implemented SCIM 2.0 surface. Point any SCIM 2.0-capable IdP (Okta, Microsoft Entra ID, Google, OneLogin, Ping, or custom) at the base URL with a tenant bearer token. See the capability matrix for the supported filter and PATCH subset.
curl -H "Authorization: Bearer <tenant-token>" \ -H "Content-Type: application/scim+json" \ https://scim.labsninja.com/scim/v2/Users
Start free. Scale as you grow. No per-seat surprises.
View Plans →