Feature Description: Replace the folders behavior by a tags behavior.
Reason: I personally don’t find the folder feature particularily handy because every item can only be put into a single specific folder (or remain in the no folder state, which is more or less also a folder). Tags basically work like folders but any item can be assigned to multiple tags instead of only one folder. I have hundreds of passwords. If I put for example paypal into the finance folder I cannot have it within the online shops folder at the same time. That’s why I basically always have to use the filter function instead.
Disadvantages: None. It is not the biggest deal but in my opinion replacing folders by tags would be helpful. If someone wants the functionality remain in a folder manner (as it is now) he can just keep assigning only one tag per item. So replacing folders by tags will not even have a negative impact for anyone. Right?
In my opinion this feature would also help for organizational items.
Kind of what everyone else says, but a wee change… I prefer that the term “tag” is changed to “label” and follow the GMail (as the most prominent example) way of using labels. A number of people in this thread seem to prefer labels over tags, and everything that is implied with labels such as using labels for “folders” and “nested folders”.
I just went through a digital cleansing of my vault which included trying to put things into folders. It was tough as many items don’t fit into a single folder.
A number of people in this thread seem to prefer labels over tags, and everything that is implied with labels such as using labels for “folders” and “nested folders”.
I agree with what you said. You have a great argument. I really think what you said makes perfect sense. So… you said everything you wish you had written. However it would be interesting to see if people prefer tags or labels.
The image illustrates a system with the concept of labels.
In my concept there should be 2 user interface screens. The first screen refers to the labels associated with the vault items. The second screen refers to the set of labels that have been created or will be created.
In the initial post I made I talked about adopting 2 systems: tag and label, here I defend the idea of the label more.
It would be nice to create labels with the following symbol: “/”, example: /label-name, /label-name/sublabel-name … and with the following symbol: “#”, , example: #label-name, #label-name/sublabel-name … or #sublabel-name - Maybe people are used to using / or # for labels
When you remove any tags or labels, you do not remove the password collection or password set. Because tag or label is a type of metadata. By removing the metadata i.e. the tag or label, you are not removing the password or the password collection. My goal here is to think about Bitwarden security. - reference, concept: “Note: Labels are different from folders. If you delete a message, it will be erased from every label that it’s attached to and your entire inbox.” That is, if you delete the label or tag, you are not deleting vault items or even a password set. However, if you remove the password set or vault items - you remove the tags and labels associated with it. (concept: Gmail labels in Bitwarden)
Optional Resources (other ideas, use cases)
It would be interesting if we had colors to highlight labels.
It would be nice to have an efficient label search engine, maybe something based on Evernote. Per example, Evernote has a very interesting tag search concept, we could use this concept to search for certain labels in Bitwarden.
Limit quantity to 100,000 tags in Bitwarden or limit to 500 labels in Bitwarden - or unlimited tags or labels in Bitwarden.
May need the drag and drop feature like in Gmail, “drag and drop labels” there is an open vote for this : drag and drop folders
Erratum
If the idea of a label system is approved and accepted by everyone, we might consider restricting the number of labels in Bitwarden, maybe something like 500 tags like happens in Gmail. “Note: Gmail allows up to 500 labels.” - reference: Create labels to organize Gmail - Computer - Gmail Help
If the idea of a tag system is approved and accepted by everyone, we might consider restricting the number of tags in Bitwarden, maybe something like 100,000 tags like happens in Evernote. “All Evernote users can have up to 100,000 tags per account. Your notes can be associated with multiple tags.” - reference: https://help.evernote.com/hc/en-us/articles/209005247-Evernote-system-limits
Preventing labels or tags from being duplicated would be a good idea
The only difference I see between folders and labels is that when you delete a label, you don’t delete the items with that label. But that’s already how folders work in Bitwarden. When you delete a folder, its contents aren’t deleted.
Tags, on the other hand, are useful because an item can have more than one tag, so that allows for more flexible categorization. I really like the tag idea.
It is been 4 years of this request and they still didn’t do it. Thinking about migrating to 1Pass so I can use labels and organize better my passwords.
Thanks for checking in! There haven’t been any changes made to folders/tagging but it is on the team’s radar. This week’s update started a round of several UI refreshes, including the ability to filter vaults in the left sidebar, and to see which item’s belong to which vault in the right column. Stay tuned!
What exactlyy is “vault item labels” on your roadmap? Is it something like tags? I surely hope and if it is, that it’s one of highest priorities.
I’m considering trying something else out because with almost 500 passwords now tags or a similar way to organize things are a necessity. I don’t know why Bitwarden team doesn’t like this feature but it’s slowly becoming hopeless that it’ll appear before my password database becomes so huge that adding tags to it in 2023 or who knows when will be a nightmare.
Hey @Destroy666, yes this would assist with large collections. You can hear the team chat more on this functionality in the most recent Vault Hours. I’ll provide an update as soon as we have information to share!
