Skip to main content
September 6, 2026

[bug?] autofill account proposition order could be way better

  • September 6, 2026
  • 1 reply
  • 2 views

Hi !

When I go to a web site with some credentials stored in 1P, the domain of the site seems to be the key to propose accounts to pick up, and this is a problem.

Our company use this naming schema: https://<tool>.company.tld
Where tool can be webmail, gitlab, www, registry, …….

When I go to webmail.company.tld the tool propose me ALL accounts under company.tld
Thus I have a huge list of accounts to select from (for webmail, for gitlab, for registry, ...)
Even worse, webmail.company.tld is not the first of the list, sometimes I have to scroll down to find it.
Even worse, The nice new splash option always select the wrong one.

This could be easily fixed:
Put first the exact url match before any other account of the same domain.
ie if I’m visiting webmail.company.tld, I want the webmail account to be the first in the list and the one picked by the spash tooltip rather than gitlab.domain.tld that have nothing to do with webmail.company.tld


I may also argue that if we have an exact match (1P has the account entry for this exact host webmail.company.tld) why even bother displaying other account just because they use the same domain.
At least put the exact match first and selected by the spash and give us the option in the settings to decide if we want the full list or not.

Thanks for listening !

Feedbacks are welcome.

1 reply

1P_Dave
1Password Employee
1Password Employee
September 8, 2026

Hello ​@Himred! 👋

Thanks for the feedback! Have you taken a look at setting an autofill behaviour for the logins that you’ve mentioned? You can set certain logins to “Only fill on this exact host” so that you only see those logins suggested on the exact subdomain. See here for more details: 

I hope that helps! 

-Dave