Google Cloud SCIM guide

Gainsight supports native SCIM provisioning, but only on Enterprise plans that typically cost $300+/user/month with custom pricing. This creates a significant barrier: customer success teams need automated provisioning to handle frequent role changes and customer data access requirements, but the Enterprise tier often represents a 2x+ price increase from standard plans. Additionally, Gainsight requires SAML SSO configuration before SCIM setup, and custom field mapping requires opening support tickets rather than self-service configuration. For customer success organizations, this pricing gate creates a problematic gap. CS teams experience high internal mobility as managers shift between accounts, and manual provisioning creates delays in accessing critical customer health data. The inSided community platform (part of Gainsight's ecosystem) doesn't support SCIM at all, forcing IT teams to manage those accounts separately through JIT provisioning.

Miro supports SCIM (the protocol that lets your identity provider automatically create, update, and remove user accounts). But SCIM is locked behind Miro's Enterprise plan, which requires custom pricing for 30+ members. Teams on Starter ($8/user/month) or Business ($16/user/month) can't access automated provisioning, even though Business includes SAML SSO. This creates a costly gap for mid-sized teams. A 50-person team on Business pays $9,600/year but can't automate user lifecycle management—they're forced into manual provisioning or an expensive Enterprise upgrade just to eliminate the security risk of orphaned accounts. Additionally, Miro's SCIM implementation can't create or delete teams, limiting automation to basic user operations.

ClickUp supports SCIM provisioning, but only on its Enterprise plan, which costs around $35/user/month (roughly $42,000/year for 100 users). Teams on the Business plan ($12/user/month) can access most premium features but are locked out of automated provisioning entirely. Making matters worse, ClickUp's SCIM implementation varies significantly by identity provider: Okta gets full provisioning with roles and teams, while Entra ID users are limited to basic user creation and removal only—no role assignments or team memberships. For the 70% of organizations using Entra ID or other non-Okta IdPs, this creates a compliance gap. You're paying Enterprise pricing but getting hobbled functionality that still requires manual role and team management. Even with SSO enabled, IT teams must manually assign users to workspaces and set permissions, defeating the purpose of automated provisioning.