You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
currently in vaultwarden it is not possible to create folders accessible to all users who can access the collection. Users can create folders to sort passwords, unfortunately those folders are only visible to the user who created them. So in order to structure large sets of data in a collection, folders are no help at all, since they are, in a sense, private. Currently, collections containing many files can get a bit chaotic - without naming conventions you are actually not capable of finding what you need, not even when using search. Also, it is hard organizing existing files, finding duplicates, and so on.
This is an issue for organisations handling multiple access-informations e.g. for b2b-customer-support. A collection for a small team supporting 50-100 customers sometimes has to handle hundreds of different encrypted files, depending on the support-level, of course. Using a single collection for every customer on the other hand is not an option, for it creates a huge adminstrational overhead.
Thus the feature-request: The existing feature of creating private folders should be extended to creating public folders, visible for all users of a collection. This would help organizing collections in a structured way. Further suggestions: Listing Folders in some sort of "table of content" within a collection, to get a quick overview of the contents.
One could argue that creating and managing some sort of table-of-content should in some cases require rights equivalent to a key-user or domain-moderator. This would not necessarily have to be done in regard of rights-management. I'd argue that most teams collaborating in vaultwarden are capable of organizing themselves well enough to collaboratively create a reasonable structure.
Perhaps, of course, there are already solutions to solve this problem - any suggestions are welcome.
Thanks in advance for your support -
kma-cloud
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
currently in vaultwarden it is not possible to create folders accessible to all users who can access the collection. Users can create folders to sort passwords, unfortunately those folders are only visible to the user who created them. So in order to structure large sets of data in a collection, folders are no help at all, since they are, in a sense, private. Currently, collections containing many files can get a bit chaotic - without naming conventions you are actually not capable of finding what you need, not even when using search. Also, it is hard organizing existing files, finding duplicates, and so on.
This is an issue for organisations handling multiple access-informations e.g. for b2b-customer-support. A collection for a small team supporting 50-100 customers sometimes has to handle hundreds of different encrypted files, depending on the support-level, of course. Using a single collection for every customer on the other hand is not an option, for it creates a huge adminstrational overhead.
Thus the feature-request: The existing feature of creating private folders should be extended to creating public folders, visible for all users of a collection. This would help organizing collections in a structured way. Further suggestions: Listing Folders in some sort of "table of content" within a collection, to get a quick overview of the contents.
One could argue that creating and managing some sort of table-of-content should in some cases require rights equivalent to a key-user or domain-moderator. This would not necessarily have to be done in regard of rights-management. I'd argue that most teams collaborating in vaultwarden are capable of organizing themselves well enough to collaboratively create a reasonable structure.
Perhaps, of course, there are already solutions to solve this problem - any suggestions are welcome.
Thanks in advance for your support -
kma-cloud
All reactions