Hello @go12 , can you share more information about these scripts? I already contacted the bitwarden support team, but i can imagine it being helpful for others if you share what workarounds are available while waiting for this feature. Without permission inheritance for nested collections, the administrative overhead is far too much, and the risk of missing mission-critical permissions is too great.
1 Like
Hi @LordPhwa, The support team is best equipped to respond. For most, the current setup provides guardrails to ensure that credentials are never assigned inadvertently. Understandably, there are multiple approaches here and more planned on the Bitwarden side in 2024.
I think it will involve something with the CLI
But ājustā add an ACL to a folder from GUI
+1 for shared folders inside collections, this feature is must requiredā¦
Dealbreaker for me not to move to bitwarden for my business
We would welcome this feature greatly!!
Why does it take sooooo long ? You are developing this feature since years.
1,5 years ago we moved from KeePass to Bitwarden, but the acceptance is dwindling among colleagues. This week a team was build to find an alternative to bitwarden. I dont know when you plan to release this feature, but I guess for us it will be to lateā¦ nice job
something really needs to be done about this.
I donāt see the immense developer overhead needed to just establish shared folders inside a collection. The current implementation of folders seems pretty useless to me, why would I spend so much effort to curate a logical folder structure for my teamās collection when they canāt see it? They would be responsible for replicating it themselves and then everyone would need to make sure they keep it up to date when any new credentials are added. Completely unacceptable if you have more than 10 credentials in a collection. I have large teams that have hundreds of credentials in a collection.
It boggles my mind that Bitwarden developers had the forethought to implement a folder system but executed it in such a shoddy way.
1 Like
Has anything been done about this yet? Its very frustrating our teams canāt create structures in their collections.
The permission management in Bitwarden is a disaster. Especially the management of permissions on collections is horrible.
Since nothing has changed since years, we will probably have to switch to another provider in the medium term.
Hi Bias, Thanks for sharing this feedback. For most, the current setup provides guardrails to ensure that credentials are never assigned inadvertently. Understandably, there are multiple approaches.
For many a nested inheritance model makes sense and there are scripting solutions the Bitwarden customer success team can share if desired. The team continues to evaluate additional options as well.
I do not understand why you state for most
Was there a questionnaire filled out?
If for most it is not applicable, then most will not change the security on the folder.
Kindly please share the scripting solution.
1 Like
Hans, You can reach out to the team via the /help page for information on the scripting solution.
Iād much rather have a warning message,
This is exacerbated by the fact that their is no way to bulk move collections to a new folder
You can bulk move items using the Web app.
You canāt bulk move Collections only Credentials - i you multi-select collations you can only change access.