Apache Superset SCIM guide

Redash, the open-source data visualization platform, does not support SCIM provisioning. Since Databricks discontinued the cloud service in November 2021, Redash is now only available as a self-hosted solution with SAML 2.0 SSO and JIT (Just-In-Time) provisioning. Users are automatically created on their first SAML login, with group membership controlled through the RedashGroups SAML attribute. While this works for small teams, it creates significant operational overhead for larger organizations that need predictable user lifecycle management. The JIT-only approach means IT teams have no visibility into who will have access until users actually log in, making it impossible to audit access rights or ensure proper deprovisioning when employees leave. For organizations using Redash for sensitive business intelligence and data visualization, this creates compliance gaps and security risks. Self-hosting requirements add additional complexity, as teams must manage both the application infrastructure and user provisioning workflows manually.

Tableau supports SCIM 2.0 for automated user provisioning across all Tableau Cloud tiers, starting at $75/user/month for Creator licenses. However, SCIM requires SAML SSO to be configured first—you cannot enable SCIM provisioning without SSO. Once SCIM is active, any changes made directly in Tableau Cloud get overwritten by your identity provider, and you cannot disable SAML configuration while SCIM remains enabled. This creates operational friction for IT teams managing mixed authentication scenarios or organizations that need flexibility in user management approaches. The SAML prerequisite means you're locked into a specific authentication flow, and the overwrite behavior can disrupt workflows when users or admins make direct changes in Tableau that then get reverted during the next sync cycle.

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.