Workable SCIM guide

Lever, the recruiting platform, does not offer native SCIM provisioning on any plan. While Lever provides SAML 2.0 SSO for authentication and supports an integration with Aquera for SCIM provisioning, this requires Enterprise pricing (~$36,778-$72,114/year for 500 employees) and adds complexity through a third-party integration. Even with SSO enabled, IT teams must manually provision user accounts in Lever or rely on the Aquera connector, which introduces another integration point to manage and troubleshoot. For recruiting teams that frequently onboard hiring managers, interviewers, and temporary contractors, the lack of native SCIM creates ongoing administrative overhead. Manual provisioning becomes particularly problematic when dealing with candidate data—a highly sensitive area where access needs to be tightly controlled and quickly revoked. SSO provides secure authentication, but without automated provisioning, IT teams face the dual burden of manual user management and potential compliance gaps when access isn't promptly removed.

Greenhouse supports SCIM provisioning, but only on Advanced or Expert tiers (starting around $6,000/year, quote-based). The bigger issue: Greenhouse's SCIM implementation only provisions users—not groups—meaning you lose the organizational structure and permission inheritance that makes identity management scalable. Additionally, you cannot fully delete users via SCIM (only deactivate), and Azure Entra users face a 40-minute sync delay. For recruiting teams managing hiring managers, interviewers, and HR staff across different departments and access levels, the lack of group provisioning creates a significant operational burden. You're forced to manually assign permissions and manage access changes for every user individually. With recruiting involving sensitive candidate data and frequent access changes during hiring cycles, this manual overhead increases both security risk and administrative workload.

Culture Amp, the employee engagement and people analytics platform, explicitly does not support SCIM provisioning on any plan. This is an intentional design decision - Culture Amp separates authentication (handled via SAML SSO) from employee data management (handled via HRIS integrations). While this approach works for their core HR use case, it creates a significant gap for IT teams managing user lifecycle across multiple SaaS applications through their identity provider. The lack of SCIM support means IT admins cannot automate user provisioning, deprovisioning, or attribute updates through standard identity governance workflows. Since Culture Amp contains sensitive employee feedback data and organizational hierarchy information that affects survey visibility, manual user management creates both security risks and operational overhead. Organizations are forced to rely on separate HRIS integrations or manual processes, breaking the unified provisioning model that most enterprises expect from their SaaS stack.