Why only one email per identity for autofill?

tmakaro

I have two identify listed. One for personal email, address, etc, and the other for just work email and work address. I have archived my work identity because I use it so rarely for autofill. My personal identity has 4 email addresses, but only the first one shows up for autofill. Why?

Sure, I could create more identities for just the other email addresses, but then I have to either duplicate my address across them or remember which one has the address info. It just seems like such an unnecessary work around.

---

1Password Version: 8.8.0
Extension Version: 2.3.7
OS Version: Windows 10
Browser:_ Firefox

ag_tommy

@tmakaro

I like to think of the identity as my personal presence at that time. I have several setup for work, home, as well as relatives and so on. Autofill fills in one swoop and you are filling the data as is. My identity contains my most used email address.

If you wish you could use something like a snippet expander (3rd party) and create several shortcuts for each email. e.g. myep myew and so forth. I have used that method and it works and keeps me sane from needing to look through potentially a lot of identifies. In such as situation you would leave the email address blank within the identity.

You might also be able to work with collections to trim any suggestions. Use collections to create custom groups of vaults

tmakaro

@ag_tommy Collections are interesting, but I only have 1 vault. This is because the family administrator can grant access to any extra vaults that I create. Or at least that used to be the case, has that been changed?

tmakaro

Nope still a problem. I really hate having extra items in my vault. The 1 email per identity just seems like a useless restriction. Like what use case benefits from it?

Joy_1P

Hey @tmakaro! If there were multiple fillable email address fields, then the extension would have to take extra time to find these fields, compare them to the fields on a form, and see if they should be filled. This can make the extension slower. It could also require users to take more steps to fill their items, and it could also lead to more filling problems across various forms (especially those that are not coded well). So for us there have been a lot of drawbacks in taking this kind of approach and we have not yet implemented it.

That said, I do understand where you're coming from, and I have added your feedback to an internal feature request that we have for this. We are always interested in bettering our product, and we appreciate you letting us know where you think we can improve.

Let us know if you have any other questions!

IDEA-I-1183