Add option to hide passwords from general search

[ashah]

I have many old passwords from old companies in my vault.

I want to keep these passwords, but I want to hide the password from the autofill UI.

It would be nice if an “archive” folder existed which I could add passwords or folders to. Then, when I needed to retrieve these passwords, I could go search the archive specifically, or I could toggle the ability to include the archive in my searches.

[Crocmagnon (Gabriel Augendre)]

You can mark their URL as to “Never” match, so they will be stored but not offered when auto-filling

[Macta]

Would be handy to remove clutter by excluding some folders (1password helpfully lets you exclude some vaults)

[abl1822]

I like this. Options to exclude items or entire folders or collections from the search would be nice. It’s also something I miss from 1Password.

[tgreer (Trey Greer)]

Would this feature cover the functionality?

Archive old accounts

There are a lot of old accounts that I own that I don’t plan on every using again. However, I want to keep them in my database in the off-chance I’ll need to access it at a random time. The problem is, it tends to clutter my search results and account lists. At this point I have hundreds of accounts in my vault, and the ability to archive old accounts would be very useful. Basically not deleting the accounts, but moving them out of the way so they aren’t accessed as easily as my regular, active…

[abl1822]

An archive feature would be nice, but I’m not sure this would cover my use case. I keep passwords for other peoples’ accounts that I rarely access as collections in an organization. Right now, I see these accounts mixed in with my own. I would be interested in a feature that lets me hide the items in these collections from the browser extension. I also have some secure notes and identities that I’d like to hide from the browser extension.

Another, separate idea that comes to mind is an ability to isolate collections from my own account’s items (something like how you can view items from only one vault or view items from all vaults in 1Password).

Edit: It may be helpful to know how I use Bitwarden… I use the desktop client to manage the stored items and use the browser extension only to log into accounts and occasionally make small edits.

[Ed2K]

That would cover it for me.

[anon15241427]

Hi Community … I hope helps @tgreer @abl1822 How are you guys?

1. Concept

1. If you have a keyword dictionary it is possible to hide your passwords from the search.
2. For example, in computer networks if you do not want to allow certain Ips to access a page you have a list called blacklist, this list is a plain text list that provides a list of Ips or a range of Ips that will not access the website
3. This blacklist is conceptually called the list of disallowed keywords…
4. So… “Whitelist” is the list of allowed keywords and disallowed keywords is “blacklist”
5. Search engines use a file called robots.txt that tells the browser or google crawler whether to search for certain words or not.
6. I hope I helped
7. Here an example: Limit search history at Bitwarden

case 1: blacklistSearchKeywordsPasswords.json

{
blacklistSearchKeywordsPasswords: [ "social1", "social2", "social3" ]
}

Notes case 1

You can’t search for things like these words as [ ‘social1’ or ‘social2’ or ‘social3’], these words preclude the search. That is, these accounts with these words are hidden from the search field

case 2: whitelistSearchKeywordsPasswords.json

{
whitelistSearchKeywordsPasswords: [ "social1", "social2", "social3" ]
}

Notes case 2:

You can only search these words as [‘facebook’ or ‘twitter’ or ‘youtube’], the rest are ignorant of the search field - passwords will not be shown

2. More notes “Options to limit password view - complete solution”

1. By allowed and not allowed keywords: “blacklist” and/or “whitelist” - Add option to hide passwords from general search
2. Archive accounts
3. Hide filters, fields, folders, tags - Limit Search History at Bitwarden
4. I think we are talking about the same things, but with different points of view.
5. References are for bibliography, I am not promoting any company, person, group or institution

3. Database rules to help

1. Feature name: Limit Search History at Bitwarden - type: “Boolean: true|false”
2. Feature name: Add option to hide passwords from general search - type: “LONGTEXT”
3. Feature name: Archive old-accounts - type: “Boolean: true|false”

4. What is the “Options to limit password viewing” feature?

1. You can have more security with search limiting, basically you hide filters, tags and folders by clicking ‘hide filters, tags and folders’ button - "low security level"
2. You can archive your passwords in the ‘archive’ folder, this prevents the password from being searched - "medium security level"
3. If you want more security, you can create a list of allowed and disallowed keywords to limit which passwords will be searched and which passwords will not be searched… - "high security level"

case 1: Add option to hide passwords from general search - options

case 1.1: Add option to hide passwords from general search - whitelist

case 1.2: Add option to hide passwords from general search - blacklist

Notes

• Blacklist/Whitelist can be called as variable allow_keyword_list or disallow_keyword_list
• If the term is something bad, we can think of something like select option “allow keyword list” or “keyword list not allowed”

5. References

1. https://www.cloudflare.com/learning/bots/what-is-robots.txt/
2. Blacklisting vs. Whitelisting | 2021 Guide | Consoildated Tech.
3. Blacklist (computing) - Wikipedia
4. https://www.esecurityplanet.com/applications/whitelisting-vs-blacklisting-which-is-better/
5. Whitelisting vs Blacklisting: What’s the difference & why it matters.