Nifty SCIM guide

Teamwork, the project management platform, does not offer SCIM provisioning on any plan. While Teamwork supports SAML 2.0 SSO through a paid Advanced Security add-on (which requires contacting security@teamwork.com to configure), this only handles authentication, not user lifecycle management. IT teams must manually create, update, and deprovision user accounts in Teamwork—a significant operational burden for organizations managing projects across multiple teams and external collaborators. This creates a substantial gap for IT administrators who need to maintain security and compliance standards. Without automated provisioning, there's no way to ensure users are properly onboarded with correct permissions or immediately deprovisioned when they leave the organization. Given that Teamwork is commonly used with external contractors and clients, manual user management becomes both a security risk and an administrative nightmare as project teams scale.

ProofHub, the flat-rate project management platform, does not offer native SCIM provisioning despite supporting SAML 2.0 SSO. While ProofHub integrates with Okta through Group Push and Schema Discovery for some provisioning capabilities, this approach is limited to Okta users and doesn't provide the standardized SCIM protocol that modern IT teams expect. The lack of documented SCIM support means organizations using other identity providers like Entra ID or Google Workspace have no automated provisioning options whatsoever. This creates a significant operational gap for IT teams managing ProofHub access across their organizations. While ProofHub's flat pricing model ($45-89/month for unlimited users) makes it attractive for large teams, the absence of proper provisioning automation means manual user management at scale—exactly when you'd most benefit from automation. Without SCIM, IT teams must manually create, update, and deactivate user accounts in ProofHub, creating security risks when employees leave and compliance headaches for access reviews.

Basecamp offers automated user provisioning only through Okta's connector, which uses a proprietary API rather than the standard SCIM 2.0 protocol. This integration is available with Basecamp's Business plan ($299/month flat rate for unlimited users), but creates significant limitations for IT teams: you're locked into Okta as your identity provider, with no native SCIM support for Entra ID, Google Workspace, or other platforms. While Basecamp does support SAML SSO across multiple IdPs, SSO alone only handles authentication—users must still be manually created and managed in Basecamp. This creates a problematic gap for organizations using non-Okta identity providers or those requiring standardized SCIM implementations. IT teams end up managing Basecamp users manually or through custom scripts, increasing operational overhead and compliance risk. The lack of true SCIM 2.0 support means you can't leverage your existing provisioning workflows or easily switch identity providers without losing automation capabilities.