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.

Scenario 1 (working)

2 apps with separate login credentials exist on separate domains or subdomains. Credentials for each are saved to ProtonPass.

When a user clicks in the login fields for either app, ProtonPass suggests the correct respective login credentials.

Scenario 2 (not working)

2 apps with separate login credentials exist in separate subdirectories of the same domain or subdomain. Credentials for each are saved to ProtonPass.

When a user clicks in the login fields for either app, ProtonPass suggests up to 3 logins associated with the domain or subdomain, not necessarily including the correct login for either app.

Desired behaviour: when a user clicks on a login for an app in a subdirectory of a domain, ProtonPass should be able to recognise that subdirectory as different from any other. So it would suggest the correct credentials for domain.com/app1/ and separately for domain.com/app2/

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...

This is extremely important to me and I believe every single Password Manager no matter what should have this critical and crucial feature; it's something that if any password manager lacks makes the password manager feel a lot less efficient to use so I would definitely love for this feature to be added as I used it all the time in the past with my former Password Manager.

This would be extremely useful. For example I would love to separate by port.

I second @Todd R's comment from August 28, 2023.

Would like to have all of the items below as options:
- "full URL" to match the whole host address, port and full path
- "exact host" to avoid matching any subdomains
- "exact port" to avoid matching services on the same host which use different ports
- "exact path" to ensure matching a for login page, and not a user management page

Subscribed to pass plus only to find out this essential feature is missing. Going to cancel my sub. I will resubscribe once this feature is added.