There is no way to remove a login item that was previously shared to a collection in an organization. Rather, removing the login item from the organization collection it stays in the family organization but gets labeled "Unassigned." The login item still shows up in the personal vault with a sideways share icon, but there appears to be no way to remove it from the organization entirely so it only appears in the personal vault where it was to begin with.
Steps to produce:
Expected result: removing a previously-shared login item from an organization should return the item to the original owner and entirely remove it from the organization.
We are moving away from tracking Bitwarden feature requests like this one as GitHub issues. We have created a Bitwarden Community Forum which has a section for submitting, voting for, and discussing product feature requests.
Please sign up on our forums, search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.
This issue will now be closed. Thanks!
Wow, no, this isn't a feature request, this is a security issue.
I found this because I'm having the exact same issue while testing. How do you removed a shared login?
I can't share a login with confidence if I can't retake control, how is it fair for me to ask the same of others.
Just going to test something...
Yup, you can edit the entry in the organization you are "no longer sharing with" and it'll update the entry in the user's personal vault.
This should be reopened as a security issue.
Most helpful comment
Wow, no, this isn't a feature request, this is a security issue.
I found this because I'm having the exact same issue while testing. How do you removed a shared login?
I can't share a login with confidence if I can't retake control, how is it fair for me to ask the same of others.
Just going to test something...
Yup, you can edit the entry in the organization you are "no longer sharing with" and it'll update the entry in the user's personal vault.
This should be reopened as a security issue.