Feature request: Option to hide value of any field

Options
RS915
RS915
Community Member

Hi guys,

I'm thinking about switching from Enpass to 1Password. I'm currently trying Windows and Android apps. However, two things surprised me.

Inability to edit order of fields/sections.
This option is supposed to be added soon, so that's cool.

However, thing that bothers me most is that it is not possible to create a field and hide its value (make content hidden like a password).

There are a lot of data that I want hidden for security reasons, e.g. different kinds of PINs, account recovery phrases or account recovery codes, 2FA recovery codes, security questions and answers, card data (number, expiration date, CVC/CVV codes) and many other various confidential data. Basically anything a user may want to keep hidden for some reason.

Let's not deal with 1Password security right now. It may be high-level, but you can never be sure that someone isn't looking over your shoulder, for example, when you have your mobile phone in your hand and 1Password app open. Another dangerous thing is screen logger - and again, let's not address how it gets into mobile or PC, it can and will record everything user opens on screen, including the 1Password app. A stranger doesn't need to gain access to your 1Password account when he can see some of data due to it not being hidden.

Due to fact that currently only value of Password and One-Time Password fields can be hidden, other data that cannot be hidden is not even visually protected enough.

I don't need to see this data every time I open app. Bottom line is to have this sensitive data visually protected with ability to reveal it just like password if I need it.

And adding aforementioned data via Password field is not a solution. It is rather a missing feature of application.

In Enpass, I can mark ANY field as Sensitive, so it is always hidden and I can only view it when I need to.

What's also interesting is that I've found several posts from users requesting this type of feature. Sad thing is that many of these posts are a few years old with statements from 1Password team members that this suggestion to add this feature will be shared with development team, but with no promises. So I'm wondering if these requests ever made it to development team when even after so many years this requested feature is still not available.

Here are some discussions that I could find according to search terms and where users are asking for this feature (or a feature on a similar principle):

June 2015 - https://1password.community/discussion/42088/hidden-custom-fields-at-secure-notes
June 2016 - https://1password.community/discussion/66075/have-a-masked-field-option-feature-request
April 2018 - https://1password.community/discussion/88341/is-it-possible-to-make-the-credit-card-numbers-be-hidden-like-the-verification-numbers-are
December 2018 - https://1password.community/discussion/99089/way-to-hide-fields-without-having-them-be-marked-as-bad-passwores
February 2019 - https://1password.community/discussion/101434/feature-request-concealable-multiline-text
October 2019 - https://1password.community/discussion/107901/mask-fields
February 2021 - https://1password.community/discussion/119241/is-there-way-to-create-the-masked-field-without-password-generator-button
July 2021 - https://1password.community/discussion/121854/feature-request-differentiate-between-password-and-hidden
February 2022 - https://1password.community/discussion/127239/feature-request-differentiate-between-password-and-hidden
May 2022 - https://1password.community/discussion/130142/no-possibility-to-hide-sensitive-info-like-it-is-for-password-fields
August 2022 - https://1password.community/discussion/133123/feature-request-notes-field-but-possible-to-hide-values-like-the-password-field
September 2022 - https://1password.community/discussion/133295/feature-request-conceal-additional-fields
December 2022 - https://1password.community/discussion/136015/conceal-any-text-field-in-a-1password-entry
January 2023 - https://1password.community/discussion/137396/feature-request-recovery-code-field-and-hidden-texts

So I don't understand why such a feature that brings an increase in user data protection is not available in app. Moreover, when it is requested. Is it really difficult to add an option to mark a field value as sensitive so that it is therefore hidden?

Thank you for your possible comments on this topic.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided

Comments

  • Hello @RS915,

    Thanks so much for trying out 1Password and passing this feedback along!

    Inability to edit order of fields/sections.
    This option is supposed to be added soon, so that's cool.

    This feature is now available in our latest beta. If you like to give it a try, you can follow this guide to use 1Password beta releases.

    However, thing that bothers me most is that it is not possible to create a field and hide its value (make content hidden like a password).

    We appreciate your additional feedback here about these requests for a feature that would allow a user to conceal any fields they chose. I can't make any promises about such a feature being implemented, but I certainly understand that this would be useful for the circumstances and field types as mentioned. I've created an Insight for the Product team detailing your specific thoughts and shared it for future consideration.

    Do let us know if you any other feedback or questions about 1Password 8. We'll be here to help!

    ref: 30872002

  • RS915
    RS915
    Community Member
    Options

    Hello Mike,

    thank you for your answer. I will look forward to the new features you add to the app in the future. And I hope that one of them will be the ability to hide the content of any field.

  • Hi @RS915,

    I appreciate the additional feedback here. With regard to the ability to conceal other fields, aside from passwords, I've let the team know this is something you'd like to see implemented as well. Thanks!

    ref: 30951686

This discussion has been closed.