Builder.io SCIM guide

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.

Gladly, the customer service platform, does not support SCIM provisioning on any plan. While Gladly offers SAML 2.0 SSO integration with enterprise identity providers like Okta and Azure AD, this only handles authentication—users must still be manually created in Gladly's admin panel before they can sign in via SSO. Even on Enterprise plans with custom pricing, there's no automated user lifecycle management, meaning IT teams must manually provision and deprovision every customer service agent. This creates a significant operational burden for contact centers, where staff turnover rates are notoriously high and seasonal scaling is common. Without automated provisioning, IT teams face delays onboarding new agents during peak seasons, and security risks from lingering accounts when agents leave. The manual process becomes particularly problematic for organizations running large support teams or multiple contact centers, where dozens of agents may need to be onboarded weekly.

Iterable, the marketing automation platform, does not support SCIM provisioning on any plan. While Iterable offers SAML 2.0 SSO with just-in-time (JIT) provisioning that can create user accounts on first login, this creates a one-way flow that leaves IT teams without automated deprovisioning capabilities. Users who lose access in your identity provider won't be automatically removed from Iterable, requiring manual intervention to verify account status and revoke access within the platform itself. This creates a significant security gap for marketing teams using Iterable. When employees leave or change roles, their Iterable accounts remain active even after IdP access is revoked, potentially allowing continued access to customer data, campaign insights, and marketing automation workflows. For compliance-conscious organizations, this manual deprovisioning requirement creates audit trail gaps and increases the risk of data exposure from dormant accounts.