Please add an option for hiding the contents of categories

Hello @RudolfSnail! 👋

Thank you for the feedback! I can see how some people would find it useful to be able to conceal more types of information saved in 1Password and I've shared your request with the team internally. Thanks for sharing your thoughts on how we can improve 1Password for your needs. 

For the time being, you might find our new Labs experiment for Android and iOS interesting: Experiment #7 - Anti-Peek Mode

-Dave

PB-46547054

I am not too happy about this, since this feature was requested multiple times in the past, and it hasn't arrived yet, so I'm doubting it will arrive anytime soon. The Android and iOS Labs experiment is not bad, but it's not the feature I'm looking for.

I found a temporary workaround that I was able to employ in Windows (haven't tested it elsewhere). I created a "password" entry, appending a meaningful name after the "password" label. This appeared to provide the toggle visibility characteristics of a password entry while giving a meaningful label.  I used it to store a passkey code that I used to enable authentication on another device. It was far easier to copy for 1Password then to hand enter the 32 character code.

I too would like to throw in my request for the ability to toggle the visibility of the contents of an entry.  This is probably the most useful for text entries; however, it could be applied to almost any entry.  Another variation would allow only the first or last few characters to be visible with the rest invisible as is presented with credit card numbers.

Adding another vote for this from the MSP side.

We recently migrated a client from Enpass to 1Password. Enpass has a per-field "sensitive" toggle that masks any field, not just password-type fields, and he relied on it heavily for things like PINs, security question answers, account numbers, and license keys. In 1Password the only workaround is retyping those fields as "Password" and renaming the label, which works but is clunky at scale and confusing for a non-technical user who just wants to flip a switch.

The result is that he isn't using 1Password. That's a lost adoption for a product we recommend to every client, and it's over a UI feature the competitor has had for years.

The field types already exist and the conceal/reveal behavior already exists for password and credit card fields. Exposing a simple "Conceal this field" checkbox on text fields seems like a small addition relative to the value, and it would make migrations from Enpass, Bitwarden, and KeePass considerably smoother. Please prioritize this.

Greg Edwards
WatchPoint