Recently, on a family plan, I can no longer delete objects in a collection. It’s just worked year over year so I’m not sure what has changed or when it changed.
I am the owner of the collections. I am configured with edit permissions on both collections. My SO has manage permissions on the collections. Has the definition of edit and manage changed from what is below?
Can edit - The user or group can add new items, remove existing items, and edit existing items in the collection, including hidden fields like passwords.
Can manage - The user or group can assign new members or groups access to the collection, including adding other members with Can manage permission, can delete collection items, and can delete the collection if they wish.
I agree that there seems to be an inconsistency between the documentation and the currently implemented behavior. Whether you are an owner/admin or not, you need “Can Manage” permissions to delete collection items using a client app.
In another thread, @priya from the Bitwarden Product Team was able to shed some light, so I hope that she will see this, as well. @priya, could you please clarify whether the description of “Can Edit” permissions in the documentation (which states that these permissions include the ability to “remove” items) is still accurate? Unless “remove” means something different than “delete”, then there is either a bug in the client apps or an error in the Help Center documentation.
If “remove” only means the ability to move the item out of the collection (to a different collection, or to the “Unassigned” category), then it would be better to use a less ambiguous word (like “move” or “reassign”) instead of the easily misunderstood term “remove”.
Hello! Thanks for tagging me, @grb. Yes, the Can Manage permission has the ability to delete items. The “remove existing items” in the Can Edit permission refers to the ability to unassign items from collections. That’s good feedback on providing more clarity – we’ll work on getting that documentation updated!