Change the Default Autofill Behavior

+1

Would also appreciate the option to specify the autofill behavior via the 1Password CLI for item creation and updates. That way we can easily adjust existing items in bulk, and set the behavior correctly from the start.

I was thinking about migrating from Bitwarden to 1Password and this is one of the biggest hurdles for me personally.

I imported my entire Vault (400+ Items) and all of them use the default "Fill anywhere on this Website" Behaviour. I do not have the time to set that manually for every single Item and from the looks of it, there is also no way for me to edit this setting programmatically, which is unfortunate.

It'd be great if this setting was added.

Also +1 for this feature request, being able to change the default in the client would make a lot of sense for a lot of companies.

For anyone taking a look here, you can now use the onepassword-sdk to update autofill behavior of items.

E.g.: when you have fetched an item from a vault you can do:

    for w in item.websites:
        if getattr(w, "autofill_behavior", None) != AutofillBehavior.EXACTDOMAIN:
            w.autofill_behavior = AutofillBehavior.EXACTDOMAIN

    updated = await client.items.put(item=item)

And then update the item. And it will change the 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.

+1  Our department (36 Customers) is looking for a new password manager. This is a make or break feature

+1

This is a genuinely useful option. Having control over the default Autofill behavior would improve usability and better match different user preferences and browsing habits.