@utility3344 I’ve moved your post into the corresponding feature request.
You might want to have a look into this other feature request too:
Reading the team’s response in post #15, I understand why a first-class Email field has been deferred to customizable item types. Introducing a true field impacts storage, encryption, sync, import and export, and presentation across web, browser, desktop, and mobile. The broader “additional item types” work is the right place to solve it properly. But perhaps there’s another way…
Instead, I’m proposing a smaller, incremental improvement: an “Add email” button on the login add or edit screen that inserts a custom field with a reserved name (email). Under the hood, it remains a standard custom field, so nothing changes about how items are stored or synced.
The value of reserving the name is that it enables capabilities custom fields do not support today. Autofill could recognize and populate email fields on websites without requiring per-user configuration. Search could also include it, so typing something like name@g… reliably returns the correct item, addressing the core concern raised in post #35. In addition, this provides a natural landing spot for email data when importing from other password managers, which is a subtle but meaningful usability improvement.
There are some UX considerations, such as prompting users when their username resembles an email and deciding what to autofill when a site only has a single login field. These are relatively contained and primarily affect the login edit experience and autofill logic rather than requiring broader system changes.
As a middle-ground option, this approach delivers immediate value to the users in this thread while leaving the larger investment on the roadmap. It also transitions cleanly into a future state with proper item types and richer data models.
The main risk is that stopgap solutions in password managers tend to become permanent. It is only worth pursuing if the team is comfortable treating this as the de facto solution for the foreseeable future. If so, this feels like one of the highest-leverage quality-of-life improvements available today.
I would like to +1 this request and make it more specific.
What many of us actually want is a default Login item template that includes three clear standard fields:
- Username
- Password
Not just “Username + Email”, but all three visible in the main form area (not in the Custom Fields section at the bottom).
Current situation feels inconsistent:
Even the Bitwarden Community Forum login screen has a dedicated Email field (see attached screenshot), yet the password manager itself still only offers one “Username” field.
This would greatly improve usability for the many services that require a separate username and email during registration.
Please consider adding Email as a native field next to (or above) the existing Username field, while keeping Username for services that still use a non-email login name.
Thanks for the great work on Bitwarden!
@Scottify Welcome to the forum!
Your screenshot was not attached. This is what I see when I go to the login form for the Community Forum:
As you can see, there is no dedicated email field — you can enter either your email address or your forum username when you log in. Thus, storing either one of these in the “Username” field of your vault entry would work — you don’t need both for purposes of autofilling your login credentials.
Similarly, websites like Amazon have an input field where you can enter either your email address or your mobile phone number; American Airlines has an input field for entering either your username or your account number. However, for autofilling purposes when logging in, the vault item “Username” field can store any of the accepted pieces of information (username, phone number, account number, email address, etc.).
Although it is common for account registration forms to collect email addresses, phone numbers, and other personal data when registering, it is usually not necessary to recite all of those pieces of information when logging in. On most websites, logging in requires only one piece of identifying information (e.g., a user name, phone number, account number, or email address), as well as a password (and optionally, some second factor, such as a TOTP code, for multi-factor authentication purposes).
Do you encounter many websites in which the login form asks for two pieces of identifying information (i.e., username and email address) to be supplied along with the password?
To your point, this is why I’m basically proposing an optional user field (a promoted version of the “additional field” near the current “username” card that lets users add additional information such as username/email as needed.
How is this different to the customizable field now? The user flow of havnig to create a third field is far too high friction relative to a single click to add the third field near the username button is. Allowing users this option essentially is the quickest/mvp work that would need to be done to resolve this long standing, highly requested user feedback.
Or just simply borrow from what other password managers do. ¯\_(ツ)_/¯
That’s true, you don’t often need both fields to log in.
However, it’s still very useful to have a separate Email field in Bitwarden when you manage multiple email addresses. That way you can clearly see and store which email address you used for that specific account, next to the username. It helps a lot with overview and prevents mistakes, especially when you have many accounts. See screenshot:
1 Like
@Nail1684 Is this possible, or has it been discussed or implemented? I was unable to find any information through my search, although I may not have search it properly.
Bitwarden does not have the ability to provide a dropdown menu with saved email addresses. There is a relevant feature request here:
@grb thanks for that. Its been 7 years from what i could gather and still not joy. Is there anything we can do to gain more attention to Feature Request?
You can read a few more topics on the forum, which will earn you voting privileges, so that you can vote for up to 20 feature requests that you would like to support. Other than that, typically the only thing that moves the needle is if there is a relevant community contribution of source code.
Come on. What’s the issue with this? It’s a no breaker.
Steps
- Website asks for Username and Email
- Create a new login for website
- Click on Username generator
- Use a service like Simple Login
- Generate & Use the new email address
- Generate password/passphrase and save login
- Fills in email field for username
At that point you have to have your own little system set up in order to remember the username for the website because some websites do not accept email address for login. They accept only the password and username. But, you can’t even do a link label because you’re linked label is tied to your username when it’s really tied to your email.
This is just an essential feature. Not having it is kind of ridiculous.