Change the Default Autofill Behavior

+1 for this request here, as well.  We have two primary use cases on my team:

1. Every host has a distinct password - for things like admin logins on ESXi hosts, we want to match specific hosts, and the bulk of our records should always ONLY auto-fill on the specific hostname match.  It would be nice to be able to change our default autofill behavior to "only match host," while allowing flexibility for more wide-ranging matches as a deviation from that autofill behavior.

Even better if we can set autofill behavior on a per-account or per-vault basis (I use 1Password for Families & 1Password for Teams, so the ability to set different default settings would be helpful on the Teams vs Families account)

Related, but distinct:

Allow setting autofill matching on subdomains of a particular tld.  I have numerous hosts with names like:

• hostname1.staging.company.com
• hostname2.staging.company.com
• hostname3.staging.company.com
• ...

We have shared service accounts across these hosts, but those shared accounts are distinct from the shared accounts for, say:

• hostname1.qa.company.com
• hostname2.qa.company.com
• hostname3.qa.company.com
• ...

It would be REALLY nice to be able to specify that a particular entry should be auto-filled for subdomains of the company.com tld - e.g.:

• "Staging Service Account" matches for *.staging.company.com
• "QA Service Account" matches for *.qa.company.com

As it is now, both of these accounts would be suggested as auto-fill candidates for ANY company.com site.