Hello everyone!
I have a problem with password storage. The browser client in Brave Browser does not save all input fields when registering new accounts. It didn’t work properly here in the forum either. You have to enter an email, a username, and a password. The username and password were saved, but the email was not saved to the vault. Can I change this behavior? I want the user, email and password to be saved.
Thanks and best regards
Vestrivan
@vestrivan Hi!
As Bitwarden’s login type vault items only have the field “username” - where you can either store a real username or an email address which often functions as a username then for many services - you can create a custom field for the email address (or a username, depending on what you store in the field “username” - and what is needed for a successful standard login with the fields “username” and “password”). See here for the topic of “custom fields”: Custom Fields | Bitwarden Help Center
I’m familiar with the custom fields. What I’d like is for the browser extension to offer me the option of saving the other input fields as custom fields when I save a new account. It’s not enough to just save a username when you need an email address when you log in. I’d also like to be able to save all the data automatically without having to think about it.
@vestrivan Okay, but then you probably shouldn’t “ask the community” but make a “feature request” (if there is not already the same or a similar feature request"). 
@vestrivan Welcome to the forum!
It seems like you are using the options “Ask to Save Login” and/or “Ask to Update Existing Login” (which can be enabled or disabled under Settings > Notifications). These functions only store the username and password, along with the website URL when a new item is created.
Personally, I recommend disabling those options, and instead using the method that I’ve described here:
If you use the above method, you can also define a text custom field to store the email address (if different from the username). If you name the custom field correctly, then the email address will be automatically transferred into the account registration form (along with your username and password) when you autofill the form as explained in Step 7 of the method I have linked above.
There is a relevant feature request topic here:
If that topic is not sufficiently similar to what you are requesting, then feel free to post a new Feature Request.
I used to use Enpass. The input fields are all transferred there. I didn’t think that this could be a new feature. I had previously searched for it and found nothing. I didn’t come across the thread with the feature request. I had actually hoped that I had only made one setting incorrectly.
Of course, @grb’s approach is a possibility, but not a very convenient one. I’m not sure I can convince the rest of the family to be so disciplined about registering new accounts.
It’s the automatic creation and changing of passwords that makes working with password managers so nice. I find it inconvenient to do everything manually.
I see the challenge - but it is the generally recommended approach (I want to say by that: not only recommended for your request)…
I want to add to that: I understand and respect your request (and there are feature requests for that). But on the other hand, your problem might be smaller than you think, because in most cases either the email address or a username plus password (+ 2FA if possible) is enough for a login. - I think I have not a single account/service, where I have to input the email address and a username for being able to login. (or maybe one or two I seldom use and am not aware of at the moment?! 
)
Though - where there’s a username - I also like to add the associated email address (then manually) to my login vault items, to have an overview, which email address it is. But again, for login mostly not necessary, I guess - but nice to know, I agree.
Understood. It often takes a fair amount of data loss before somebody becomes paranoid. You may need them to first complain about losing credentials before they will be willing to listen to the more bullet-proof approach to creating accounts.
In other words, sometimes you need to let them touch the hot stove.
No password manager can (reliably) automate the process of creating and changing passwords, because every website requires a different procedure for accomplishing this task. At best, a password manager could build a database of password change/creation algorithms for some subset of websites (perhaps the most popular ones), and then select the algorithm based on the active URL — however, this approach is not scalable, nor sustainable (the functionality would break every time that one of the supported websites rolls out a redesigned interface).
Perhaps you didn’t actually refer to this type of automation, but were merely impressed by the fact that information was automatically transferred from the web page to the password manager in Enpass. Bitwarden can do this, but it only uploads the password and either the username or email address; as noted by @Nail1684, for 99% of websites, this is sufficient for logging in (for example, you mentioned this community forum login — all you need for logging in is your email address and password — I never need to supply my username grb when logging in).
Be that as it may, the method that I linked to is also “automatic” in the same sense — information is automatically transferred between the the web page to the password manager (only the direction of transfer is now the opposite: from Bitwarden to the web form).
If one counts up the number of required mouse clicks, the approach that I recommend is actually more convenient. And if your family members are sufficiently disciplined to fill out an online account registration form correctly, perhaps there is hope that they can fill out a Bitwarden login creation form also (which — with time — should be easier to do, because the form to fill in is identical each time they create an account, something that is decidedly not true when manually filling in online account registration forms).
That being said, I understand that for someone who has not previously used a password manager (or for someone who has previously used a different password manager), it can be quite a paradigm shift to get in the habit of initiating the account creation process in the browser extension rather than in the web form.
The bottom line is that @Nail1684 is right: this “problem” is not nearly as consequential as you currently believe it is. The vast majority of websites do not require more than two pieces of information (username or email, as well as password) for the primary authentication.