ADP 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.

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.