It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Forum Discussion
ProratedMongoose
8 months agoNew Contributor
How do I disable 1Password guessing a username on new login item creation?
A somewhat recent update seems to have made 1Password make an assumption about the username for new login items. For a variety of reasons, it has been wrong 100% of the time for the dozen plus login ...
- 4 months ago
Hello everyone,
I'm happy to share that, with the latest update to the stable version of 1Password (8.10.78), our team has added a setting to turn off the prefilling of usernames when creating new items in the app:
You can find instructions on how to update here: How to keep 1Password up to date
Thanks again for all of the feedback and for always helping us make 1Password more useful for your needs and your workflows.
-Dave
1P_Dave
Moderator
8 months agoHello ProratedMongoose! đź‘‹
Thank you for reaching out! When you create a new Login item, 1Password will now automatically fill your email address in the username field and generate a password. Username suggestions are based on the vault that you’re creating a new item in and are suggested based on frequency of previous use in that vault.
You can read more about this new feature on our blog: 1Password product enhancements [Winter edition]: Mobile improvements, better item creation, and even more security features
I've let the team know that you'd like an option to turn this feature off. The team plans to add ability to directly choose which email address is suggested based on your default identity. This new functionality is currently being tested in the beta version of the apps and will make it into the stable version soon.
-Dave
PB-46615313
accordionmelody
6 months agoDedicated Contributor
I’d like to add my voice to this topic.
I understand that the pre-filling of the username field is meant to make it easier to create new logins.
However, it doesn’t take into account that users (especially privacy- and security-conscious users, who are likely a core target group for 1Password) use different email addresses (aliases or “hide-my-email” addresses) or different usernames for different logins.
In fact, in a blog post from December 3, 2021, you even recommended using different usernames for different logins—just as passwords shouldn’t be reused.
With that in mind, this feature (which unfortunately has no opt-out option) is problematic and, for many users, doesn’t solve a problem but instead creates new ones.
Personally, every time I try to create a new login, I get a username suggestion that I’ve only used once and that doesn’t even appear in my identity entry. I’ve specifically created a default identity entry that contains neither a username nor an email address—but even that workaround doesn’t seem to work for me.
Additionally, I have to point out that several core aspects of using a password manager have unfortunately become quite frustrating recently:
- Creating new logins with automatically suggested usernames that can’t be disabled and often give unwanted suggestions
- Unwanted opening of entries in edit mode after launching the app (I believe this has been fixed)
- Moving multiple elements within an entry (fields or sections) not being saved correctly (there are several bug tickets and forum posts about this)
All of this is making the user experience increasingly frustrating for me.
For me, it’s important that upcoming updates really focus on these core aspects and bring bug fixes instead of introducing new features.
Even though it might remain just a wish, it would be great if 1Password introduced a legacy management feature that allows designated trusted individuals to access an account in the event of death (a long-standing request—Proton Pass plans to introduce such a feature in the coming months).
As a long-time and enthusiastic user of 1Password, I’m sadly a bit disheartened by the feeling that I’ve recently been forced to test more and more unfinished and immature features—or run into bugs that really shouldn’t be part of a final release that gets rolled out to what are likely millions of users.