Personio SCIM guide

BambooHR does not support inbound SCIM provisioning on any plan. While BambooHR integrates with identity providers like Okta and Entra ID, it functions as the HR source of truth that provisions users TO other systems, not the other way around. This means your IdP cannot automatically create, update, or deactivate user accounts in BambooHR based on HR events or group membership changes. BambooHR offers SAML 2.0 SSO with JIT provisioning, but this only handles authentication for users who already exist in the system. This creates a significant operational gap for IT teams managing employee lifecycle automation. While BambooHR can push employee data to your IdP when HR makes changes, there's no way to automate the reverse flow - provisioning new users into BambooHR itself still requires manual account creation or CSV imports. For organizations where BambooHR isn't the primary HR system of record, this means maintaining dual data entry processes and accepting the compliance risks that come with manual provisioning workflows.

Namely supports SCIM provisioning through Okta's integration, but there's a fundamental mismatch: Namely is designed as an HR source system that provisions to other applications, not the reverse. While SCIM functionality exists, it's primarily intended for Namely to push employee data downstream to apps like Google Workspace or Office 365 via Okta's HR-driven IT provisioning workflows. For IT teams that need to provision users into Namely from their identity provider, this creates a gap. The available SCIM support isn't designed for inbound provisioning scenarios. Plus, with pricing starting at $9/employee/month but enterprise features requiring custom pricing that typically runs $19-26 per employee per month, you're looking at significant costs for an HR platform that may not align with your provisioning architecture.

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.