case 1: If the user wants to use tags to organize their accounts, they can use this symbol: #tag-namebecause many social networks by default use something like this for #tag-name tags. We can see this on social networks such as Twitter, Facebook, Instagram and Youtube.
Want to make folders and subfolders? Use this symbol /folder-name, /folder-name/subfolder-name ...
case 2: In Wiki.js, for you to create folders and subfolders you create something like this - you would use this symbol: \folder, \folder\subfoldernote: Wiki.js doesnāt call it a label, it calls it a folder or subfolder, folders and subfolders are context dependent, example: \folder, \folder\subfolder. reference:Gmail system is similar to Wiki.js system | Wiki.js system is similar to Gmail system.
note: Both Wiki.js and Github.com use the / symbol to create folders and subfolders.
Want to make labels? you do something like:
3.1. If the user wants to use labels to organize the accounts, he can use something like this, something like this label in Gmail
Perhaps in addition to tags, it is necessary to create specific labels. Because tags can be difficult to remember and search. With too many tags users can get confused. Best in this case is to allow the user to have a specific label or set of sub-labels. These labels and sub-labels, in turn, can replace folders and subfolders. If you want to consider creating a folder or subfolder as a label and sublabel an alternative would be to use this symbol /label/sub-label/sub-sub-label ...
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!
