I'll use proton pass when this feature will be available. For now, proton pass is unusable for me

Just another human chiming in that Proton Pass isn't valid or usable for me without, at the very least, subdomain/host-based differentiation for logins.

Yes that's essential to me as well

This is absolutely critical if you host multiple services with different authentication on multiple subdomains, like I do. I don't quite get why this isn't already implemented.

I still want get prompted to autofill the main login page, to NS1 for example, but NOT have a proton icon on every field on subsequent pages because then I am creating DNS records and never want that saved and the fill box is small enough without a icon in it I have to work around. I disabled for this site now, so my work is much less impacted but I lost my autofill on parent login page. Specifically, keep autofill on https://my.nsone.net/#/login but disable on https://my.nsone.net/#/connect/dashboard or anything else https://my.nsone.net/#/* thats not "login". So either allow exact only match, just not domain, or allow regex I can exit to exclude as my regex skills permit.

Adding a regex option for matching could solve it for all.

This is a must have feature. Hoping this can happen ASAP.

This really is a crucial feature. Just allowing us to match by hostname (e.g. I want to match against "foo.bar.com", not "*.bar.com") would solve 99% of usecases.

This isn't just a self-hosted thing (though I use it for that as well) - there are many services that have a "companyprefix.appname.com" format, where you very often have many accounts for. This includes ubiquitous things like Slack, or anything logging in via Auth0.

This feature would be very much appreciated. I set up Proton Pass but realized this did not work. It is too crucial of a feature.

This is what's keeping me from switching from Bitwarden right now. Crucial for self-hosting when you have several logins at the same domain but at different ports.

If you self-host some stuff this is crucial!

Please! I have many services run locally at my home on different ports

I have different services on their own subdomains and each have their own logins. But when I try to login to sub1.domain.com it suggests logins for sub2.domain.com, sub3.domain.com, and sub4.domain.com. But the browser plugin only shows two suggested logins and how often do you think it’s the right one?

Good to see I am not alone, can't use Proton Pass without this basic functionality. Have mentioned it in every feedback/survey, in some forums, but been waiting since first launch for it to get implemented, quite ridiculous it's still not done while other less important stuff (admittedly that's subjective) has been added already. Sticking to Bitwarden like many others.

This is the configuration that keeps me in Bitwarden for the moment

This is a feature I can't live without. This is one of the main reasons I can't use Proton Pass as my main password manager.

I forgot about how incredibly useful this feature in Bitwarden is ... until I started testing Proton pass.

First internal site I wanted to login to had over 30 matches.

The next page I logged into is this one here to vote for this feature.

This feature is critical for me for business uses; and has been a massive pain point since trying to move from BitWarden. Many of our internal systems are under the same domain:

customer1-release.company.com
customer1-develop.company.com
customer2-release.company.com
customer2-develop.company.com

etc.

This often results in the situation that autofill is completely *useless* for anything related to our business. It also inevitably results in many 'Do you want to update this password?' messages that are completely unrelated to the active website.

Subpath recognition would be awesome

The inability to distinguish logins across subdomains is a significant roadblock to adoption. Frankly, a little surprised this product went GA without that functionality considering it's prevalance as a standard feature for like products.