I’m just migrating to BitWarden from LastPass and have imported all of my passwords from a CSV file. I’m currently in the process of sharing some of the folders with an organisation however I came across an issue where after moving passwords to an organisation, the folder in my vault has no items, so I delete it. This however deletes the folder from the organisation also meaning that I have to leave emtpy folders within my personal vault.
Just wondering if there is a workaround or anyone else has experienced this?
Hey there, folders are more like tags (for your personal view only) and only used to organize the items you have access to, that can include both individual vault items as well as organizational vault items.
Folders will be replaced by ‘vault item labels’ in a future update.
Shared items in an organization are contained within collections (shared folders)
Thanks for coming back to me on this. Ok, makes sense so I guess the recommended approach for me would be to utilise Collections in an Organisation rather than folders to keep everything organised?
So I think it is but the only issue is relating to the fact that folders can nest things. In our Example we might have a “Clients” folder which holds different folders for each individual client to allow them to be found a lot easier.
Creating a collection for each client is also beneficial due to the allowed fine grain control of it. Overall the issue I had originally was just due to the fact that I can see folders within my organisation but they feel tied to my individual user on a team account. I’ve added a video below to kind of demonstrate what I mean.
Vidyard Recording? - As you can see, everything came in within a folder. If I move an item into the organisation it goes out of my personal vault, which is as I would expect. The folder on my vault is then empty. But if I go into the organisation vault and look the VPN folder is also there. Lovely, that’s what I want. But then if I delete the VPN from my Vault it disapears from the organisation, thus making things a little less organised.
Oh, nice. Thanks for that, didn’t realise you could nest Collections
I can also see that Folders are specific to a user, not an organisation so nested collections feels like the way to go here. Thank you for all of your help!
Today I wanted to move an item placed in a folder to my organization. This worked fine and it appeared in a new folder with the same name in the organization.
Since a folder for a single item is overkill, I assigned it to “No folder” and deleted the now empty folder.
To my surprise, this also removed the same folder in my private vault. Fortunately the entries there were not deleted but only unassigned from any folder.
What is the correct way to perform those actions? Should I remember to move the item out of any folder before placing it in the organization?
Will the deletion of the organization folder have any effect on folders in other user’s private vault? I hope that this is impossible because of the limited access.
@marlin Welcome to the forum! I moved your post into the existing thread on the same topic. to avoid duplication.
As explained in the responses above, organizations do not have folders. Thus, the folder that you were using (and which you later deleted) never existed in the organization, only in your individual vault.
A folder can contain items from the individual vault as well as items from an organization vault. When you view the contents of a folder, it may be a good idea to set the vault filter to “All Vaults” (this will allow you to see everything that is in that folder).
You should have left the folder in place if you still wanted to use it for your individual vault items.
There is no such thing as an “organization folder”.
I just performed the steps mentioned above again and now I know the source of my confusion: After removing the last item visible to the organization, the folder was still listed when viewing only items of that organization. A refresh of the page fixes this.
In my opinion this is a UX issue that can be easily resolved in at least two ways:
Display a warning if a folder is about to be deleted that contains items currently not displayed.
Hide a folder in an organization as soon as it no longer contains any visible items.
