Can't make the switch without this feature.

At least, subdomain matching like 1Password should be available, as it significantly improves the user experience.

For a homelab, sub-domain or full string matching is a must!

Can't believe this is still under review for 2 years now.

For local service this is a critical update.

I am a new user of Proton pass and got all the way in before I found this problem. I was very enthusiastic about Proton pass up until I saw what was happening with the sites that use multiple subdomains (such as Chase). This feature alone is going to stop me from recommending Proton Pass to others.

Will not buy proton until this is implemented . 80% of my passwords , are for internal / company / self hosted or otherwise strange services, where at least the starts with is essential

As a user managing multiple subdomains under my primary domain, I find this feature essential. Currently, Proton Pass suggests ALL saved logins whenever I visit any subdomain — even though I use different credentials for each subdomain.

In Bitwarden, I could elegantly solve this issue using the "Host" setting, which ensured that only credentials specifically matching the visited subdomain would be suggested.

This functionality is critical for both security and usability. Without proper URL matching rules, I'm forced to select the correct password manually from a cluttered list every time, which is inefficient and error-prone.

The current behaviour creates unnecessary friction in my workflow and potentially introduces security risks if I accidentally select the wrong credentials.

Please implement this feature — it's indispensable for anyone with a structured login system across multiple subdomains!

I use a single domain to self host dozens of applications, it's extremely annoying that all my items show on every subdomain.

Please give us a way to limit items to specific subdomains.

I have a bunch of logins for websites that have started using Shopify to handle their logins. The main site's URL isn't even part of their login page anymore, so Pass has no idea what I'm logging into. Currently the choice is to either manually search those logins every time, or add Shopify's URL to every site so they ALL show up as login options. Neither is ideal.

I know a solution would be to log in with a single Shopify account for all of these, but that's exactly the kind of thing I'm trying to get away from by using Proton - separate aliases for each account, etc.

Holy crud, this was originally posted on Jul 28, 2023. How is such a critical feature such a low priority?
Really hard to ever trust moving to Pass from 1Password when you're so far behind and take so long to implement these features.

I think this is the one feature that is stopping me from migrating from 1Password to Proton Pass, just DON'T do it like Dashlane!

This is the biggest drawback when switching from 1Password. This and not having cc autofill and being able to store software licenses.

I self host and wanted to try to use proton pass (mostly for the email alias generation and integration with proton mail) but the fact that i go to my TLD and see 24 autofills is a pretty big flop...

This basic feature still hasn't been implemented? 🥱 Come on guys, this is a nightmare for self-hosters, devs, and unsuspecting users using a company or institutions self-hosted services.

I tried to switch over to Proton Pass permanently, but this was a huge issue for me. Seems like it's under review so hopefully we will have it soon!

Would like to have this feature Yesterday!

As so many other, I have domains with different logins for subdomains. Becoming unworkable this way.

guys this is SO important!

Having the matching by subdomain should be a basic feature for any password manager