Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Solved
New item login field already populated
Hi, When I create a new item in the Linux, Android and iOS 1Password apps, the login field is already populated with an email address and focus is set on the password field. How to change that? I w...
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
ModeratorHello Spacehog! 👋
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 under "Better item creation and navigation - New item creation flow": 1Password product enhancements [Winter edition]: Mobile improvements, better item creation, and even more security features
The current expected behaviour is for 1Password to automatically generate a password and fill it into the password field when you create a new item.
-Dave
Just a question, does marking your answer as a ‘solution’ mean that you are no longer taking the comments below as serious issues with this new feature? I see many users like myself that would like to see this feature as optional. But I notice that every topic around this issue has now been marked as solved (which it is not in my opinion). It feels like you’re shutting down the discussion. I get that developers often see users as annoying (just kidding), but we do have a serious point here. Using aliases is quite common these days and meant to keep us safe. Which I understood to be your mission too. What happens with all our feedback now?
- 1P_Dave
Marking a post as a solution to a thread doesn't mean that the issue/request itself is solved or closed. It's a way to highlight the most up-to-date answer for anyone who stumbles onto the thread in the future.
Everyone's feedback will continue to be passed along to the team, the discussion remains open, and we'll continue to answer questions and collect feedback going forward. 🙂
-Dave
