AutoFill Email in new entrys

[Factless (Benjamin)]

Dear All,
I’ve searched the forum for a few minutes but found nothing like the question I have.
Is it already possible to autofill my email as username for new entry’s? In 90% of my cases, I use my email as username and therefore it would be great if that’s auto filled on new entry’s in the Bitwarden app.
If it’s not already possible, I’m going to add this as a feature request.
Thank you!

[dh024 (David H)]

Hi Benjamin - welcome!

This feature has been requested before, and I believe there was a community member working on a fix for this. More here:

[deleted link]

[Factless (Benjamin)]

Hi David,
thanks for the fast answer! So I’m going to wait for the feature to be implemented!

[Teduardo]

Hi, wondering if theres an update on this feature? As new logins are added ongoing (and particularly when setting up for the first time), it would be FANTASTIC to be able to select and autofill email addresses stored in my personal contact card to use as my username rather than typing each and every time (i’m using the iOS app).

[agamon]

Hello, is there an update for this? LastPass had this and it was very useful

[grb]

There is a Feature Request that you can vote for, here:

Autocomplete default username (+random password) when creating new entries (or option in generator)

When creating new entries, I always have to type in the same old email addresses and usernames that I use with almost every other site. It would be great if there was a way to speed up this process, for examples with an autocomplete functionality on the username that suggests commonly used usernames from your other entries. What it could look like: [bitwarden--username-autocomplete] There are two ways I could see this working, either the data from the autocomplete comes from what you’ve used…

[LampQuarter]

Bumping this to the Top

When, please?

[Neuron5569]

AutoFill Email in new entrys

There is a Feature Request that you can vote for, here:

Seems like the most realistic way of getting a feature is to get someone external to contribute, and even that isn’t guaranteed as someone internal has to be willing to own the feature (maybe if it is heavily voted). The usual reasons are: small team, corporate subscription as the main revenue driver, internal priorities, etc.

[LampQuarter]

I understand the reasons and agree. With that in mind, I would update the request to offer a default email address. In my experience, I use the same email address more often than not. That feature should be pretty easy to implement and support;