TinyPulse SCIM guide

Microsoft Viva Glint (formerly Glint) does not support SCIM provisioning at all. Instead, it relies exclusively on Microsoft Entra ID native integration, which only works if your organization uses Microsoft 365 and Entra ID as your primary identity provider. This creates a significant constraint: users must be manually created in both Entra ID and Viva Glint with matching email addresses, and a Microsoft 365 Global Admin must register Viva Glint in your Entra tenant. Organizations using other identity providers like Okta, Google Workspace, or OneLogin are completely locked out of automated provisioning. The Entra ID dependency creates real operational friction even for Microsoft-centric organizations. While SSO authentication works through Entra, the user lifecycle management still requires manual coordination between your identity team and HR administrators. Survey population management and manager hierarchy synchronization—critical for employee engagement platforms—become manual processes that don't scale with organizational changes. For companies using multi-IdP environments or non-Microsoft identity solutions, Viva Glint essentially forces a choice between automated provisioning and your preferred identity architecture.

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.

Aha! Roadmaps, the product roadmapping platform, does not support SCIM provisioning on any plan. While Aha! offers SAML 2.0 SSO integration with identity providers like Okta, Entra ID, and OneLogin, this only handles authentication through JIT (Just-In-Time) provisioning. The critical limitation: JIT provisioning creates user accounts with no default role or access permissions, requiring administrators to manually configure access for each user after they first sign in. For product teams managing strategic roadmaps and stakeholder access, this creates significant operational overhead. Since product roadmaps contain sensitive strategic information and stakeholder access typically varies by product area, IT administrators must manually assign appropriate roles and workspace permissions after each user is provisioned. There's no automatic deprovisioning when users leave the organization, creating potential security gaps. This manual process becomes particularly problematic for larger product organizations where dozens of stakeholders across different business units need carefully managed access to specific roadmaps.