Bitwarden collections9/20/2023 ![]() If your project team members need to share passwords, learn how to use Bitwarden's Folders feature. This may have changed as I haven't used LP in maybe 2/3 years, but if someone needed access to a login in the shared folder, but nothing else, we had to create a new shared folder and a new login, causing duplication and confusion.How to use folders in Bitwarden to manage passwords for project teams I preferred this to how LastPass did it, where you could have sub folders in a shared folder, and they would all be treated with the same permissions for all who have access to the main folder. This allowed us to share specific folders with specific users/groups. For example maybe some in finance needed access to the bank account, but not everyone in finance, or maybe a coop student or intern needed access to specific logins/collections. We had the shared collections setup based on department, and maybe this is more a small/medium company issue, but sometimes there would be overlap or folders with logins in them some in that department would need, but we wouldn't want to share the whole folder structure with the employee(s) in question. Then we set the hierarchy and all share permissions and it was pretty much smooth sailing from there.Īt first I thought this wasn't ideal compared to how LastPass did it, and it still could be improved, don't get me wrong, but in time I came to appreciate it, as it gave us more control over individual folders/collections. After discussing with my boss we decided to get the different departments to cleanup their folder structure and try and streamline the hierarchy to cut down on the amount of folders/collections needed. with their own specific permissions, so it maybe a little annoying as an admin to have to go in and set the permissions for each folder/collection. Now this maybe a pro or con depending on how you look at it, but BitWarden will still treat both of those collections as separate collections, i.e. Both collections can have sites and you could create further sub folders as needed. This should then result in a collection called Test Folder 1, and a sub folder in that collection called Test Folder 2. So, to have a collection "sub folder" (for example), create a collection called " Test Folder 1" now create another collection called " Test Folder 1/Test Folder 2" (sync/refresh app if needed to see changes). This resulted in organized shared collections in BitWarden when users went to My Vault > Collections. When I imported the folders from LastPass to Bitwarden it created collections, and when there was a sub folder in the collection (could be multiple sub folders) it would create a collection with the "folder name"/" sub folder name" (example below). It does appear BitWarden sort of supports this. Our LP org had lots of folders organizing most logins. Part of that transition was the export of logins and folders from LastPass to Bitwarden. Our company transitioned from LastPass to BitWarden (I being the IT guy doing it). As others already stated, collections (shared) are different than folders (not shared, specific to user, they can change them however they want without affecting others), at least in BitWarden terminology, but I figure you get that, you're just trying to figure out how to share stuff and keep it organized in folders, er collections.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |