Can I make the Chrome browser extension subdomain sensitive?

Thank you for this post since this is a pain point for us as well

I'm wondering how a big organisation is using 1Password when there is no subdomain sensitive autofill of domains.

Let me give you an example:

projectone.somedomain.com
projecttwo.somedomain.com

Both projects have an "admin" login.

With tagging we would tag one admin item with "project one" and the other one with "project two".

The one admin item would get "projectone.somedomain.com" as a domain and the other one "projecttwo.somedomain.com".

The autofill mechanism would now suggest two "admin" items. And now the guessing game begins.

Yeah sure we could name the items "Project One / admin" and "Project Two / admin" but this is quite cumbersome.

And this simple example shows how 1Password is lacking very simple organisation features like folders, vaults in vaults etc. and the missing subdomain sensitivity in the autocompletion makes this even worse.

In the end I don't get how big companies seriously use 1password with this lack of organisation features.