Leadpages SCIM guide

Instapage, the landing page builder platform used by marketing and growth teams, does not offer native SCIM provisioning. While Instapage supports SAML 2.0 SSO integration with Okta and OneLogin, only the Okta connector provides any provisioning capabilities—and even then, it's through Okta's proprietary connector system rather than standard SCIM. This creates a significant gap for IT teams managing multi-vendor SaaS stacks, as you're locked into Okta-specific provisioning that doesn't work with Microsoft Entra, Google Workspace, or other identity providers. The lack of universal SCIM support becomes particularly problematic for organizations using Instapage across marketing teams. When team members join, leave, or change roles, IT administrators must manually manage access in Instapage separately from their primary identity provider workflows. This manual overhead increases security risk—former employees may retain access to landing page creation tools and customer data—while creating compliance gaps for organizations that need automated audit trails.

ADP Workforce Now does not support inbound SCIM provisioning as a target application. Instead, ADP functions as an HR source system that provisions users TO other applications through third-party bridges like Aquera. This creates a fundamental misunderstanding in the market—while ADP integrates with identity providers like Okta and Azure AD, it's typically pushing employee data OUT to provision accounts in downstream systems, not receiving provisioning requests from your IdP. ADP supports SAML 2.0 and OIDC for SSO authentication, but user accounts must still be manually created and managed within ADP's HR platform. This architectural reality creates significant operational overhead for IT teams. When new employees join or leave the company, their ADP records must be manually maintained by HR staff, while other applications can be automatically provisioned through your IdP. This breaks the unified identity lifecycle management that SCIM enables, forcing organizations to maintain split processes where some apps provision automatically while their core HR platform requires manual intervention.

Google Analytics does not support native SCIM provisioning at the application level. While GA4 360 customers can leverage SCIM through Google Cloud Identity at the organization level, this creates a fundamental gap: SCIM provisions Google accounts broadly, but Google Analytics access requires property-level permissions that must be managed separately within the GA interface. Even with Google Cloud Identity SCIM in place, IT admins still face manual property access assignments, role management, and the complexity of coordinating between Google Workspace provisioning and GA-specific permissions. This layered approach creates operational overhead and compliance risks. When employees join, leave, or change roles, their Google Analytics access may persist even after their broader Google account is deprovisioned, since property permissions are managed independently. For organizations using non-Google identity providers, the challenge is compounded—they must maintain federation between their IdP and Google Cloud Identity, then separately manage GA property access.