please don’t get us wrong, we love your product and continue to do so. But please give us an ETA or realistic intel about when you will implement the AUTO-inheritance-function for groups on nested collections!
Nested collections is a beginning. I don’t understand the problem why a nested collection can’t also have subfolders as there is a separate folder structure for the personal vault.
We want to switch to Bitwarden from our many Keepass workgroups. In our work group there are 6 subfolders in Keepass and each of these has between 0 and 10 sub-subfolders.
Arranging everything in a flat hierarchy makes Bitwarden inflexible compared to Keepass.
We switched from keypass to bitwarden some years ago and still have the nested look from keypass as we just exported/imported all. Its a mess and cleaning up isnt that easy as you need to do a lot manual.
Can you please create folders under a collection so we can differentiate our clients and their systems in bitwarden properly
I am a consultant, I have a lot of customers, I would also love if every collection has its own folder nest.
In fact, it would be great if we could export collections. For example, I have a Customer A collection, once I finish my work, I export the collection, i give the collection to the customer and I delete it from my vault.
I would like to see “collection-folders” (or how ever to call them to make them distinct from current “my vault folders”) rather then the nested-collection feature with complicated ACL. It’s always simpler to have ACL only set at the root level (=collection) and no nested ACLs at all.
Not be able to structure the collections easily is the biggest disadvantage of using bitwarden for us.
(Also the need to switch to the web-vault to create collections is a hurdle we dislike. If nested collections is the future, make the creation easier by supporting it in the apps).
Currently Bitwarden has been undergoing some web UI enhancements and changes.
As I understand this is part of a multi phased UI refresh to hopefully make Bitwarden a bit more intuitive and streamlined.
Perhaps better ACL management and auto-inheritance for nested collections will be on the horizon, asi know it is something that has been requested here before.
The current 2022 roadmap lists Org Admin Vault Refresh on the list of priority improvements, so not entirely sure what that means but hopefully easier management in the vault for Org admins!
I was demonstrating how cool Bitwarden was to my co-worker and the first thing she said was… “why cant I organize the passwords in our organization’s collections into folders?” Organizing items into folders with inheritance is something everyone just expects as standard now a day. Im sure its a difficult process to implement if it has not been done yet, after 4 years of this post being open. For the non-tech folks, this would be such a big improvement.
Thank you for making such a cool product!
It would be great if we could see some kind of an eta on this. My company wants to switch but our teams have a lot of collections. This would reduce the amount of administration. For now we do it manually with the nested collections but its more work.