Forum Discussion

majortom's avatar
majortom
Occasional Contributor
12 months ago

Feature suggestion: Better way to manage/maintain Recovery Codes

Hello,
this is not related to 1PW for windows but more for the complete 1PW Plattform.

I suggest a better way to manage/maintain Recovery Codes. Many services like Google, GitHub etc... provides Recovery Codes if you lose your Password.

Currently I save them in the notes field. Is this the best way? I think not.
At the moment I don't know what the better solution might be, but I think you should think about it.

What do you think?

BR, Tom

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

windows

3 Replies

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    11 months ago

    majortom

    Thank you for the feedback, I've filed a feature request on your behalf with our Product team. 🙂

    -Dave

    ref: PB-41029566

  • majortom's avatar
    majortom
    Occasional Contributor
    11 months ago

    Hey, imho the comment field with visible plan text is no good way to store imporant things like recovery codes.

    If I could wish for it, I would prefer to have a multi-line "password field" or a new option "Recovery Codes" under "add more". To avoid wasting a lot of space, the recovery codes should only be displayed in the UI when you click on the field.

  • 1P_Gem's avatar
    1P_Gem
    Icon for 1Password Team rank1Password Team
    12 months ago

    Hi majortom! I understand that you'd like a better way of managing recovery codes for your saved logins, rather than using the Notes field.

    I can definitely understand how improvements here would be useful, and I'd be happy to file this as a feature request with our Product team. Could you tell me a little more about why your current workaround of using the Notes field isn't working for you? Would something like a multi-line concealed Recovery Codes field be more in line with what you're looking for?

    The more details you can provide, the better, as this will allow us to understand user needs and figure out what a best-case resolution to this might look like 😄

    I look forward to hearing from you!