Notion SCIM guide

Amplitude supports SCIM provisioning, but only on Growth plans (starting around $36K/year) or Enterprise plans with custom pricing. While Amplitude's SCIM implementation covers the core functionality—creating, updating, and deactivating users—it requires SCIM to be specifically enabled for your organization, and regenerating the SCIM key immediately invalidates existing integrations without warning. For product teams on Plus plans ($49/month), upgrading to Growth just to unlock SCIM means jumping from under $600/year to $36,000+/year—a 60x increase. That's often more than the entire analytics budget for smaller product teams. The gap becomes particularly problematic for cross-functional product teams where analysts, PMs, and engineers need varying levels of access to user behavior data, but manual provisioning creates security risks around sensitive analytics permissions.

Bugsnag supports native SCIM provisioning, but only on Enterprise plans with custom pricing. This creates a significant cost barrier since you must upgrade from Business ($475/month for 1M events) to Enterprise just to unlock automated user provisioning. For many engineering teams, this represents a substantial price jump for provisioning features that should be standard across all paid plans. The Enterprise requirement is particularly problematic for mid-size development teams who need error monitoring automation but don't require Enterprise-level features. Without SCIM, IT teams must manually provision developer accounts and manage team memberships for project access—creating security gaps when developers change teams or leave the company. OneLogin users face an additional limitation: SCIM isn't supported on Enterprise instances, forcing a workaround through the standard Bugsnag app.

Greenhouse supports SCIM provisioning, but only on Advanced or Expert tiers (starting around $6,000/year, quote-based). The bigger issue: Greenhouse's SCIM implementation only provisions users—not groups—meaning you lose the organizational structure and permission inheritance that makes identity management scalable. Additionally, you cannot fully delete users via SCIM (only deactivate), and Azure Entra users face a 40-minute sync delay. For recruiting teams managing hiring managers, interviewers, and HR staff across different departments and access levels, the lack of group provisioning creates a significant operational burden. You're forced to manually assign permissions and manage access changes for every user individually. With recruiting involving sensitive candidate data and frequent access changes during hiring cycles, this manual overhead increases both security risk and administrative workload.