Add "Username" and "Email" as separate entries for (vault) login items

Feature Requests Password Manager
23

This :arrow_up::arrow_up::arrow_up:
I can’t believe it isn’t yet implemented, I have to manually create a custom field any time the login has a email+username format

1 Like
24

This is the only thing that’s keeping me from switching from Enpass to Bitwarden.

The way that Enpass does it is ideal IMO. When creating a login there’s separate fields for email, username, password, URL, phone number, security question/answer, tags, notes. Even though most of these will be unnecessary most of the time, they’re available in the creation menu, so you don’t have to add a new field each time. Obviously, once you create and save the login, it’ll only display the info you’ve filled in until you want to make edits.

Enpass’s approach is having all the most common fields available at the start when creating a login, and then allowing the user to just fill in what they need without having to create custom fields for things that are relatively common. This is the most convenient and least frustrating way to do it. It would make a world of difference for me, and I’m sure many other users.

2 Likes
25

I created an account just to request this. Really silly that it isn’t implemented yet.

1 Like
26

When I want to include an email address in addition to the username used to login, I just create a new text field. It’s simple and allows me to reference the values I need, but does not impact the ability to login with the username.

27

I also want to request that the Email field be added as a default field to the “Login” item type.

If the username field does not contain an @ symbol, than the moment the field is clicked or tabbed out of, the “Email” field should become visible between the “Username” and “Password” fields.

It would also be nice to have optional Security Question fields.

28

I’m really hoping this request will be implemented! It’s already quite old, but I’m optimistic. I asked about it yesterday and was referred here. When I registered the account for this forum, I didn’t realize the email wasn’t saved, so it got deleted.

29

Hi,

I am using an email relay service to protect my main email address. This means I have to generate an email for every site I create an account on. This is quite an hassle on Bitwarden at the moment, since Bitwarden treats usernames and emails as something, where you either need the one or the other, but never both at the same time.

It would be way more comfortable, if the username and email field would be separated, so that you optionally can generate each for every webpage, without having to resorting to copy and paste.

Thanks!

2 Likes
30

@reoccur1 Welcome to the forum! (and I think I forgot to welcome you on the other thread…)

Two things:

  1. To use two separate fields for now, you could use custom fields for a given login item (to add the “other component” - username or email): https://bitwarden.com/help/custom-fields/
  2. There already is a feature request regarding two separate fields: Add "Username" and "Email" as separate entries
31

@reoccur1 I now merged your post with this existing feature request as it seems to reflect most of what you are requesting. If you have another separate feature request from that, feel free to open a new one.

32

Yes, it seems to be about similar thing. My focus tho is on making the generation of relay email addresses easier, as I sometimes need to generate the username and(!) the email. And yes, I am using customs fields for that right now.

Thank you

33

Then as I wrote before: feel free to create a new feature request regarding exactly that.

(BTW, a feature request should always be about more or less one specific thing, as a vote must be relatively unambigous… with two or more “requests” in a feature request, the question would be “what would I vote for here?”)

34

This!! I’ve been using Bitwarden for years and I literally made an account for this forum JUST to say this!! It drives me crazy to have to put either the associated username or email in a note for each password when it would be so simple for them to just add another field (or even an “add email” option within “add new custom field” that autofills for “enter your email” boxes).

It’s also very ironic that this site itself even has a separate email and username

3 Likes
35

This please. I’ve lost several accounts because the extension saved the username but not the email while the site required it for login, or vice versa.

I currently put the extra username/email in the note field, but the problem with notes or custom fields is that they are not convenient for quick searching because you need to type the full word to find it. Unlike the standard username field, the results appear instantly as you type part of the text. For example when I type name@g I can see all the accounts registered with name@gmail.com if their emails are saved in the username field, but I have to type the full address name@gmail.com to get the accounts whose emails are saved in notes or custom fields to appear in the results.

1 Like
36

Alternatively, you can use a wildcard: name@g*

37

That’s a useful hint, although it requires a few more key presses.

Additionally, if I’m not very careful about formatting in my notes, I might have written down something like email:name@gmail.com. Since you can’t search for middle part of text that isn’t separated by spaces, eventually the search keyword needs to become *name@g*.

So in order to not miss the 5% of emails written as notes, basically I need to type additional special characters in every search, which reduces the ease of quick searching.

For now, I just edit all the email addresses that I put in notes to name@g so they appear as soon as I type to g. But it would be helpful for this situation if email became a default field and used the same search method as username.

2 Likes
38

Why is it 6 years later, and this very simple request has not been implemented.
In the worst case add an option in settings ‘add seperate username’ and then make it available in items when this is turned on. It is for sure not difficult to implement, at worst needs an extra entry in DB that default to empty.

The past time I wished that I could use this as either the email needs to manually be set in notes and can’t be autofilled anywhere or username needs to be in notes and manually filled.
The now recommended option seems to set them in custom fields but this is not the same as it can’t be instantly accessed like email and password. Depending on the platform also needs scrolling.

I am now seriously considering switching to enpass while I love bitwarden for everything else.

2 Likes
39

It’s infuriating that we still have to add Email field manually.
Would be nice if the yearly payment amounted to some level of development from Bitwarden team, but it seems like there’s nearly 0 QoL features added.

Autotype is another feature still MIA.

1 Like
40

@Anvi Please take a minute to review the Community Guidelines, which do not allow baseless accusations to be made; violation of the posted rules can get your posts removed from the forum.

To be clear, even though your favorite feature request has not been implemented, there certainly have been a steady stream of new “QoL” functionalities added (some notable ones added recently include: file attachment exports, browser extension UI persistence, inline autofill menus, etc.). Autotype is actively being worked on right now.

41

A post was merged into an existing topic: Autocomplete default username (+random password) when creating new entries (or option in generator)

42

Currently, Bitwarden supports two main fields for login credentials: Username and Password. While custom fields exist, they don’t integrate into the autofill process as seamlessly, and the Linked field option only mirrors existing values (username or password).

Many websites require three separate credentials during signup:

  • Username

  • Email address (separate from username)

  • Password

Right now, users must:

  • Create a custom field and manually copy/paste the email, defeating the purpose of a password manager.
  • Type the email as a note.
  • etc

Feature request:

  • Add Email as a first-class field in login items, alongside Username and Password.

  • Autofill should natively support populating all/(any of the) three fields on websites that require them.

  • This improves usability, avoids manual copy/paste, and future-proofs Bitwarden for sites requiring multiple identifiers.

2 Likes