Dashlane SCIM guide

Keeper Security supports full SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing (typically ~$60/user/year for 100+ users). Teams on Business plans ($3.75/user/month) get SSO but no automated provisioning - meaning IT admins must manually invite, assign teams, and manage vault access for every user. When employees leave, deprovisioning only locks their vault rather than deleting the account, creating ongoing security visibility gaps. This creates a significant gap for password management governance. SSO alone doesn't solve the provisioning problem - you still need manual processes for onboarding, role assignments, and vault permissions. For security-critical applications like password managers, manual user lifecycle management introduces compliance risks and delays that undermine the zero-trust model most organizations are trying to achieve.

LastPass supports SCIM provisioning starting at the Business tier ($7/user/month), with integration support for all major identity providers including Okta, Entra ID, Google Workspace, and OneLogin. However, LastPass SCIM has critical limitations around deprovisioning: when users are removed, their vault access isn't immediately revoked, and shared folder permissions become complex to manage at scale. This creates a significant security gap for IT teams. Password vaults contain the most sensitive credentials in your organization—API keys, service accounts, privileged access passwords. When employees leave or change roles, their access to these credentials must be revoked immediately, not left accessible while IT manually cleans up vault permissions. SSO alone doesn't solve this because it only controls login authentication, not ongoing vault access or shared resource permissions.

8x8 supports SCIM 2.0 for automated user provisioning, but only on their quote-based X Series plans (previously $24-44/user/month range before they moved to custom pricing). While SCIM can create, update, and deactivate users, it has critical gaps that create ongoing manual overhead: license assignment must be done manually after every user is provisioned, users can't be deleted (only deactivated), and provisioned users don't automatically appear in the Company Directory. For IT teams managing a unified communications platform that typically covers all employees, these limitations defeat much of SCIM's purpose. You're still manually touching every user account to assign licenses and ensure directory visibility. The lack of user deletion support also creates compliance headaches when employees leave - accounts accumulate as "deactivated" rather than being properly removed.