Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Password entry gets converted to a Login entry
I have a Password entry that I want to create and I want to use an email address as the User Name. There is no web site address associated with Password entry, but upon entering the email address and...
Thanks for following up with us jdguilty.
While I can't speak to the design decisions for the Password item, I've personally seen a few scenarios where the option to convert the item has saved someone from recreating it as a Login. For example, in a situation where it would be helpful to autofill the password, using a Login item is a better fit. That said, I can understand why you'd want an item to stay the type you chose. I can't promise that this is behaviour we'll change, but I've shared your feedback with the team. Thanks again for including your use case on this.
If you'd like to create Password items with usernames, you can add a text field while editing the item (+ add more > Text), then enter the username there. You can also rename the text field as "username" or anything else. As long as the default username field is empty, the item will stay as a Password item.
1085747
1P_Dave
Moderator
ModeratorHello jdguilty! 👋
Thanks for the question! This is expected behaviour: adding a username to a password item will change it to a login item. Password items are meant to store passwords that aren't associated with a username, like a password for an encrypted folder or the combination for a lock.
Is there a reason why you'd like to keep an item that has both a username and a password as a password item? I'd be happy to pass along your feedback to the appropriate team.
-Dave
That seems to be a little inconsistent with the way you currently have the Password items established. When I go to create a new Password entry, one of the default fields available is "username". If the user, as you say, adds a username then it automatically gets converted to a Login. Then why even make that username field available ln a Password entry from the get go if the entry is going to be converted to a Login entry? I guess I've always associated a website with a Login item. And you also have website as a default field on a new Password entry. I'd line to be able to create a Password entry to store my username and password that I use to access my wife's computer. Granted, some would consider that as a Login entry but I'd rather just store it as a Password entry that uses a username. I should be able to have that choice where to store the entry, not have 1Password dictate it for me.
- 1P_Timothy
Community Manager
Thanks for following up with us jdguilty.
While I can't speak to the design decisions for the Password item, I've personally seen a few scenarios where the option to convert the item has saved someone from recreating it as a Login. For example, in a situation where it would be helpful to autofill the password, using a Login item is a better fit. That said, I can understand why you'd want an item to stay the type you chose. I can't promise that this is behaviour we'll change, but I've shared your feedback with the team. Thanks again for including your use case on this.
If you'd like to create Password items with usernames, you can add a text field while editing the item (+ add more > Text), then enter the username there. You can also rename the text field as "username" or anything else. As long as the default username field is empty, the item will stay as a Password item.
1085747Although I don't like the auto-conversion to a Login item when adding a value to the "username" field for a Password item, I can live with the workaround. I've tried it and it works. I guess you can't fight 1Password city hall :-). I'll get off my soapbox now. Case closed.
