ProofHub 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.

Nifty, the project management platform, does not support SCIM provisioning on any plan tier. While Nifty offers SSO integration (Google SSO on Pro plans, Microsoft SSO on Business plans, and custom SAML 2.0 on Enterprise plans), these authentication solutions don't address user lifecycle management. IT teams must manually create, update, and deactivate user accounts across all Nifty workspaces, creating operational overhead that scales poorly as project teams grow and change. This manual provisioning approach creates significant compliance and security risks for organizations managing multiple projects with rotating team members. Without automated deprovisioning, departed employees may retain access to sensitive project data, timelines, and client information. For agencies and consulting firms that frequently onboard and offboard team members based on project needs, the lack of SCIM provisioning turns user management into a time-consuming administrative burden that increases the risk of access control failures.

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.