Zoom SCIM guide

Slack supports SCIM provisioning (the protocol that lets your identity provider automatically create, update, and remove user accounts). But Slack restricts full SCIM functionality to Enterprise Grid—its top-tier plan that costs ~$230/user/year and requires custom pricing negotiations. Teams on Business+ ($180/user/year) get SSO but no automated provisioning, creating a manual management burden that defeats the purpose of centralized identity management. The pricing jump from Business+ to Enterprise Grid represents a 28% increase plus the complexity of Grid's multi-workspace architecture. For a 200-person team, that's an additional $10,000/year just to unlock automated user lifecycle management. Once you upgrade to Enterprise Grid, Slack's policy is permanent—no downgrades allowed, ever—making this a high-stakes decision that locks you into their most expensive tier indefinitely.

Linear supports SCIM 2.0 for automated user provisioning, but only on its Enterprise plan with custom pricing (typically $192-240/user/year). The company requires SAML SSO to be enabled before SCIM can be configured, meaning you can't use automated provisioning without also implementing single sign-on. For teams currently on Business ($9.60/user/month annually), upgrading to Enterprise represents a 20x price increase just to unlock basic provisioning automation. This creates a significant gap for growing teams that need automated user lifecycle management but aren't ready for enterprise-level pricing. While Linear offers JIT provisioning through SAML, this only creates accounts when users first log in—it doesn't handle deprovisioning when employees leave or role changes that require immediate access removal. For compliance-focused organizations, waiting for users to self-provision on first login isn't acceptable.

LastPass supports SCIM provisioning starting at the Business tier ($7/user/month), with integration support for all major identity providers including Okta, Entra ID, Google Workspace, and OneLogin. However, LastPass SCIM has critical limitations around deprovisioning: when users are removed, their vault access isn't immediately revoked, and shared folder permissions become complex to manage at scale. This creates a significant security gap for IT teams. Password vaults contain the most sensitive credentials in your organization—API keys, service accounts, privileged access passwords. When employees leave or change roles, their access to these credentials must be revoked immediately, not left accessible while IT manually cleans up vault permissions. SSO alone doesn't solve this because it only controls login authentication, not ongoing vault access or shared resource permissions.