The feature was requested in 2018, and now we’re in 2025. Is there any chance it will be developed, or do we know if it’s on the roadmap for the coming years? It would be great to have it, as I believe it should be a fundamental feature.
1 Like
Any update on this highly requested feature? i found some Parent Permissions script on their Github but good luck on tracking that for over 12k passwords and over 120 collections. GitHub - bitwarden-labs/admin-scripts: Leverage scripts with the Bitwarden CLI to automate admin tasks
Yep I agree, the script is way too limited. I tried pimping that script a bit to fetch my needs (specified above) but more urgent tasks took priority… I’ll see if I manage to get back at it soon.
Anyway, some kind of ETA for this feature, should it be concerned at all like something BW wants, would be nice!
The lack of inherited permissions really confuses the users. Maybe when a new collection is created we need a pop up box that asks users if they want to copy permissions from the parent collection.
@bw-admin @go12 Is there an ETA for inclusion of this FR? It’s officially been 7 years since this request was created and promised many times over the years.
I’m also a KeePass user. Inheriting permissions on sub-collections is a must.
We have a need to keep login credentials for each of our customers in it’s own area (collection). Folders don’t work because from my understanding are not shared with other users. KeePass allowed us to created folders for each customer to track their credentials.
Wrote a GUI tool that roughly does the same as the parent permission inheritance script from bitwarden’s admin-scripts.
Allows me to have child permissions inherited from parent collections (not dynamically of course).
It’s a v0.0.1 so feedback, features requests (and/or help) are welcome.
See GitHub - netinvent/bitwarden_cli_toolkit: Quick and dirty GUI for collection permission inheritance
For the record, I’ve revised the title of this feature request to better reflect what is being proposed (previous title was: “Nested Inheritance: Shared subfolders to organize items inside collections”; revised title is: “Inheritance of Access Permissions for Nested Collections”).
Hello,
Is there any update on this topic please?
Any update on this? Seems like such a basic feature to have.
1 Like
Proposed Solution: Flexible Permission Inheritance
I strongly support this feature request. The ideal solution would be to allow an admin or owner to choose whether permission inheritance is enabled when they assign a user or group to a parent collection.
To make this even more flexible, when an admin does enable inheritance, they should also have the ability to explicitly deselect specific child collections that should be excluded from inheriting those permissions.
This design would offer the perfect balance of simplicity and control:
-
Simplicity: Admins could enable inheritance for a parent collection to quickly grant access to its entire nested structure in one action.
-
Granular Control: Admins could still “opt-out” specific, sensitive child collections from that inheritance, allowing for deliberate, individual permission assignment only where it’s needed.
The Problem with the Current Design
The current system, which never allows inheritance, is extremely cumbersome, especially for organisations with deep and wide nested collection structures. It forces admins to manually assign permissions for every single child collection.
This design has an unintended, negative consequence. It’s similar to forcing a mandatory password rotation every month. The intention is good (improving security), but the result is bad (it encourages users to set weaker, simpler passwords to cope).
In the same way, Bitwarden’s intention is to provide granular control. But the result is that admins are encouraged to create less isolated, less secure structures (like putting everything into one single collection) just to avoid the overwhelming task of managing permissions.
Edit: This proposal is rephrased with the help of LLM, but the idea is original.