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

I love Proton but as a developer, I have soooo many logins on the same domain... Dev and QA credentials, test accounts for different types of users, etc. Having every single one of those show up whenever I try to log in to any environment of any of our apps is immensely frustrating and was something I was hoping to get away from when moving to Proton.

Really hope we can get this feature implemented or I'll have to start looking at other options for password management.

Proton Pass stores URLs differently than 1P. How does Proton Pass ensure that login information is not inserted into a fake site?

I find it interesting that it is assumed by Proton that a top-level domain is specific to one account/password. Subdomains and port numbers for that matter, are most definitely associated with different logins. I do not like it that Proton Pass lists ALL of my logins associated with my TLD, regardless of the fact that I have different logins associated with the subdomains. Surely, this is just an oversight, rather than a deliberate "feature"? Let's get this fixed, so that I can stop using Bitwarden. I really want Proton Pass to be clean and crisp.

I'm one this feature away to switching from bitwarden (new bitwarden looks bad for me)

This is a much needed feature. I am hesitant to full move over from LastPass at the moment because of it.

My needs match Farid and several other commenters. Currently juggling 20+ different sets of credentials for my self-hosted services. Please please please add this feature. I've been a Proton supporter for years, and while my continued support does not hinge on this, it would be greatly appreciated.

Pretty crucial feature. I have switched from 1Pass and I want Proton Pass to support this. I have same issue with my work related credentials where they are mostly under same domain but different subdomain for different web apps.

Proton Pass dev team, Please include this feature...