Currently, when moving an item to a shared collection, the item remains in the “sharer’s” initial folder as expected but appears in no folder for all other “sharees”.
Desired would be for the item to initially have the same folder in the sharees password manager as it is in the sharer’s. Changing the folder by any member of the collection will continue to be independent.
@hax A very belated welcome to the forum!
I’m going to close this feature request for now (with some delay), as folders are part of the individual vault – and no other member of the organization has access to the individual vault of others. So a new item can’t access and influence that area.
(–> Folders | Bitwarden)
That limitation should not be an issue.
One possible solution: Assigning to a collection adds metadata to the item that includes the name of the source folder. The client app for each member of the collection will see a new item (perhaps based on timestamp) that is not in a folder and can do what it wants with the metadata including checking to see if that member has a folder with the same name and then putting the entry in that folder if it exists. The sharer is not accessing anything of the other members and doesn’t even know if the item did indeed end up in a folder. Alternatively, show the name of the source folder as a column in the collection’s item list and allow each member to click a button to move the item and even create the folder if it doesn’t exist. At the very least, seeing a source folder name makes clearer what the item is for.
The current solution of not using folders in collections by default creates a big mess for virtual companies (and others) that make use of a huge number of web apps that don’t necessarily work with Okta or are sharing with many users of varying organizational skill levels. On-boarding new users is also a mess.
@hax Thanks for the response and further clarification – and though personally I remain sceptical – I re-opened this request.
Overall it seems you are interested in a more easy sharing mechanism, so I would like to point out this other feature request also: Vault Item Sharing (different from the current Org/Collections implementation)
