Gladly SCIM guide

Builder.io, the visual CMS platform used by developers and content teams, does not offer SCIM provisioning on any plan. While Builder.io provides SAML 2.0 SSO integration on their Enterprise tier with identity providers like Okta, Azure AD, and Google Workspace, this only handles authentication—not the automated provisioning and deprovisioning of user accounts. IT teams must manually create and manage user accounts in Builder.io, then separately assign appropriate permissions for different Spaces and projects. This creates a significant operational gap for organizations using Builder.io across multiple content teams. Without SCIM, departing employees retain access to Builder.io Spaces until manually removed, creating security risks around content management systems that often contain sensitive marketing materials and website code. The manual overhead becomes particularly problematic when managing access across multiple Builder.io Spaces, each requiring individual permission management for developers, marketers, and content editors.

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.

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.