Iterable SCIM guide

Adobe Marketo Engage does not support native SCIM provisioning with Okta, despite being widely used by marketing teams in Okta environments. While Marketo offers limited SCIM support through Azure AD or Google Workspace via the Adobe Admin Console, this leaves Okta customers with manual user provisioning workflows. Even with Okta's integration offering "Group Linking, Schema Discovery, and Attribute Writeback," users still must be manually created in Marketo before SSO can work—creating a significant operational gap for IT teams managing marketing technology stacks. This limitation is particularly problematic for enterprise organizations where marketing teams frequently change, contractors need temporary access, and compliance requires automated deprovisioning. The lack of Okta SCIM support means IT admins must maintain separate provisioning processes for Marketo while automating everything else through their identity provider. Adobe's focus on their own identity ecosystem through the Adobe Admin Console effectively creates vendor lock-in for automated provisioning capabilities.

Pardot (now Marketing Cloud Account Engagement) does not offer direct SCIM provisioning. Instead, it relies entirely on the Salesforce platform's identity management system. While Salesforce does support SCIM at the platform level, this creates a complex dependency where IT teams must manage Pardot users through Salesforce's broader ecosystem. This means you need Salesforce platform access and must navigate Salesforce's SCIM implementation, which can be unnecessarily complex for teams who only need to provision marketing users into Pardot itself. This platform dependency creates significant operational overhead. IT teams must either grant broad Salesforce admin access to manage marketing users, or constantly handle manual provisioning requests through Salesforce. The integration assumes you're already deep in the Salesforce ecosystem with dedicated platform administrators, which isn't always the case for companies using Pardot as a standalone marketing automation tool.

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.