Pardot SCIM guide

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.

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.

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.