BlueJeans SCIM guide

Google Meet doesn't offer SCIM provisioning as a standalone service because it's integrated into Google Workspace, where SCIM is handled at the organization level. While Google Workspace Business Standard and above plans ($14+/user/month) support SCIM provisioning, this manages entire Google Workspace accounts—not granular Google Meet access controls. IT teams can provision users into the broader Workspace environment, but can't control specific Meet features like recording permissions, meeting hosting capabilities, or attendance policies through SCIM. This creates a significant gap for organizations that need fine-grained control over video conferencing access without managing full Google Workspace lifecycles. The real-world implication is that IT teams must either provision entire Google Workspace accounts (expensive and potentially excessive for Meet-only users) or manually manage Meet-specific permissions and features. This becomes particularly problematic for organizations with contractors, temporary staff, or role-based access requirements where different user types need different Meet capabilities. The lack of granular provisioning also creates compliance challenges for industries requiring audit trails of who can record meetings or host sensitive discussions.

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.

Bill.com offers inconsistent SCIM provisioning support that varies dramatically by identity provider. While Okta users can access SCIM provisioning through the OIN integration, Bill.com doesn't publish native SCIM documentation, and other IdPs like Entra ID are limited to SAML SSO only. This fragmented approach means your provisioning capabilities depend entirely on your IdP choice rather than Bill.com's platform features. For finance teams managing sensitive AP/AR workflows where user access directly impacts invoice approvals and payment processing, this inconsistency creates operational gaps—especially when onboarding new controllers, AP clerks, or accountants requires manual role assignment tied to spending limits and approval hierarchies. The real problem is that Bill.com gates all SSO functionality behind Enterprise plans with custom pricing (typically 2-3x their Corporate plan at $79/user/month), yet still provides no clear path to automated provisioning for most customers. Since financial systems require precise role-based access controls for SOX compliance and segregation of duties, manual user management creates both security risks and administrative overhead. When employees change departments or leave the company, orphaned accounts in payment systems pose significant financial and compliance risks that manual processes often miss.