Change the Default Autofill Behavior

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.

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.

+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.

our web dev shop has a team of three.  all the passwords show for every staging site because they are all on the same main domain (cloudways).  Two years in it's absolute chaos.  Need to be able to:

• Set the default to exact domain
• Bulk edit all the records to exact domain

Looking at this thread i'm probably going to get customer serviced with "ill tell the product team" and then nothing will happen, so is there a way to do that with the api / developer tools? 

There is also no bulk-edit option to change this setting for a bunch of entries (I imagine it would be difficult to implement).

But we're faced with long, rote, click-clicking away to update every annoying entry.

Lots of IP based stuff that has no business going 192.168.0.*, as an example.

Here's another one: How about searching for entries with the wide setting? For us, only very, very, few, entries should be widely appicable.

Thank you everyone for the continued feedback and feature requests. 🙂

-Dave

ref: PB-45841039

corbosman Well, there is something to say for having the current default. As a consumer you might have the same account on all subdomains from a domain.

But indeed, for a company (we are a marketing/website-company and have hundreds of customers with their own [customername].[our-stagingdomain].nl site. For every staging-domain, we add (multiple) logins to 1Pass, and need to remind ourselfs to set the subdomain setting.

It's just unnecessary extra work. :(

I don't really understand why the 1password team doesn't implement this. It seems like a must-have feature. Any business that uses 1password probably has subdomains under their primary domain. We have dozens if not hundreds. And it's beyond annoying that it's not by default locking subdomains to only the subdomain. To the point where many of my colleagues simply refuse to use 1password.

I am in the exact same boat, I have been pushing for this feature on these forums for getting on 2 years now.

I would truly love to see the feature get implemented because when you are working with large numbers of sub-domains this would make life so much easier. 🤞

Thomas1234 Well, since this issue dates back to march 2023, I stopped keeping my fingers crossed.

From a developer-point of view, it doesn't seem like a huge change. But somehow apparantly it either is a big change, or 1Password just don't want to change it.

I don't get it. There seems to be a lot of interest in this option, but all we hear is "we'll notify our Product team".