Skip to main content
C
Chris_
June 8, 2026
Solved

Don't merge *.company.com. Treat company.com as a top level domain.

  • June 8, 2026
  • 1 reply
  • 47 views

We've purchased 1password business to help employees manage internal passwords. Many of these systems are on the same *.company.com domain. 1Password keeps linking these different systems into the same record.

Creating records and then manually changing the "Only fill on this exact host" option is extremely clunky. 

How can we:

  1. Set a default option for all our users for 1Password to always match on exact host?
    or
  2. Make 1Password treat our internal domains (e.g. company.com, company.local) as top level domains - ideally this would be a policy we can configure?
Best answer by 1P_Dave

Hello @Chris_! 👋

Thank you for the feedback! While I can't make any promises, I've filed a feature request on your behalf to have our product team look into adding a feature to set "Only fill on this exact host" as a default for your organization. 

For the time being, setting "Only fill on this exact host" manually for any items using that domain would be the best workaround. 

-Dave

CFP-16506

1 reply

1P_Dave
1P_DaveAnswer
1Password Employee
June 8, 2026

Hello @Chris_! 👋

Thank you for the feedback! While I can't make any promises, I've filed a feature request on your behalf to have our product team look into adding a feature to set "Only fill on this exact host" as a default for your organization. 

For the time being, setting "Only fill on this exact host" manually for any items using that domain would be the best workaround. 

-Dave

CFP-16506

    Terms & ConditionsAccessibility statement

    ©2026 1Password. All rights reserved.
    4711 Yonge St, 10th Floor, Toronto Ontario, M2N 6K8, Canada