Any updates on the implementation of this feature? What’s the current status and time line to deploy a feature to remove an orgaizational user from Bitwarden and their personal vault based on a deleted (A)AD-account?
Focus on self-hosted variant.
1 Like
We desperately need this feature.
2 Likes
Any updates on the implementation of this feature? What’s the current status and time line to deploy a feature to remove an organizational user (based on an AAD-account) from Bitwarden and their personal vault automatically, once the AAD-account has been deleted?
This is about the self-hosted variant.
We really do need this feature, we must ensure we do automatically remove these data once the AAD-account is gone. With five-figure users there’s no option to manually take care of this task.
We’re in need of this – Bitwarden is a nightmare to manage at scale when offboarding users. Revoked users should be blocked from logging in (personal and organisation) and have their existing sessions deauthorised. Deleting the user should remove both the personal and organisation vault.
1 Like
@bw-admin Please, can you comment on the latest replies to this conversation? Please include information about the current status of the development and time schedule for release of this urgently needed feature.
@bw-admin Still no comment to this thread form Bitwarden. Please, can you comment on the latest replies to this conversation? Please include information about the current status of the development and time schedule for release of this urgently needed feature.
This is a feature, that’s urgently required in enterprise scale installations of self-hosted Bitwarden with users in the thousand or tens of thousands.
What’s on Bitwarden’s roadmap?