[Feature Request] Change default autofill behavior

skint007
skint007
Community Member
edited January 22 in Windows

It would be nice to be able to set the default fill behavior for new items. Right now, it defaults to "Fill anywhere on this website". At work and in my home lab, I have so many different credentials that need to be used that use the same base domain that it gets kind of crazy with how many suggestions I get, many times requiring me to scroll endlessly and search for the specific credential.

I can fix most of this by selecting "Only fill on this exact domain", however when you have hundreds of credentials that need to function like this, and it not being able to change the default behavior, it makes it very tedious to have to change this for 99% of our stored credentials.

On a side note, would there be an easy way to do bulk edits of our credentials in our vaults using the CLI to change the behavior of the autofill?


1Password Version: 8.10.23 (81023003)
Extension Version: 2.19.0
OS Version: Windows 11
Browser: Edge

Comments

  • Hello @skint007,

    Thanks for your feedback and feature request for a way to change the default autofill behavior.

    I understand that given your scenario, that this type of feature would make short work for changing this behaviour for all of your current items and when new items are created. I'll pass this along to the Product team for consideration.

    Please let us know if you have any other suggestions.

    On a side note, would there be an easy way to do bulk edits of our credentials in our vaults using the CLI to change the behavior of the autofill?

    I'm not sure if this is possible, but I've forwarded this question to the appropriate team. I'll get back to you once I know more.

    ref: PB 37942744

  • ag_mike_d
    edited January 24

    Hello again skint007,

    I've got my answer from the team and currently adjusting the autofill behaviour is only possible within the 1Password apps and not with CLI.

    As noted I've filed your request with the team. Thanks!

This discussion has been closed.