-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto folders when collection shared #45
Comments
Thanks for the feedback. |
The problem here is that folders are user specific and are not in the realm of sharing. Folders are encrypted with the user's encryption key, not the organization's (like collections). Because of this, no other user (like the org admin) can add or edit a user's folders. Two ideas: One approach here is to add a button for a user to click from their vault that will allow them to "Create folders from collections" that will setup a folder structure that matches the current collections. Of course this would only be a one time thing and newly added logins to those collections wouldn't automatically follow. A user could periodically click the button to re-organize them though. Another alternative is to allow the client applications to just browse the vault based on the organization, where things are organized by collection rather than folders. This is already done in the web vault (Shared page). |
I am also evaluating bitwarden with the view of rolling out the premium version to our company. Even if the collection name were to show up as the folder ? |
This is no longer necessary since we sync all collections and their structure down to user devices. |
When a new collection is shared with a user it would be helpful to have an option as the user or the admin to automatically have the collection added as a folder.
I am looking at this as a new company about to use the product. I am likely to create a number of collections to be shared with the staff. The collections will already be in the groups the users would likely want the passwords managed as folders. As I can see most users when they are first shared their list of passwords to never move the logins into folders as its too much work when faced with a list of 100+ new logins.
The text was updated successfully, but these errors were encountered: