When saving a new password, the title of the entry should be the site/service/app name, not the full URL. For example, saving a FB login would show Facebook as the entry title, not www.facebook.com/login as the title.

This will stop me from switching to Proton pass

Almost 3 years now. 🥳

I really like proton pass but this is really painful to have to go over dozens of credentials before finding the good one, especially on phone because the priority is something like "latest used" and we always have to open proton pass to search for the correct credentials.

Coming from 1Password I realise how much I miss and need this functionality.

Like ZohoVault and LastPass, too. It's not just domain-matching, but FQDN-matching (Fully Qualified Domain Name). i.e. it should be able to distinguish between:
- aslon1222.blah.local
- swedb0011.blah.local
- mx10.sub.blah.local

This seems like basic credential hygiene that any serious password manager should handle.

Currently, Proton Pass does not differentiates saved credentials based on subdomains, only on domains. That can result in inconveniences for users that have different credentials on different subdomains.

I.e:

"service1.domain.com" has user "user1" and password "password1"
"service2.domain.com" has user "user2" and password "password2"

As it is of today, if I get to the login page of service1 or service2, both the credentials will appear as options on the Proton Pass browser extension. The annoyance in fact is that if you have N credentials in N subdomains of "domain.com" you will have to get the exact option from the list of N options that Proton Pass will display.

The best behavior it seems, would be if Proton Pass displayed only the credential saved for the subdomain you are trying to log into at the moment.

*Edit: Upon further looking, it seems that the current subdomain is always on the top of the Proton Pass credential options, so it isn't that much of a hassle. Will leave this as a suggestion, even though it is not important for me.

This is the sole reason I am not switching to proton pass. Please implement this!

I mean come on ...

Maybe someone at proton can give an update on this request? As a programmer myself I cant imagine that this would be a huge undertaking to implement. I think having an option to force 'exact match' on the url would suffice in the short term. Maybe it could be triggered by a parameter added to the associated url string.

Another disappointed previously-a-Bitwarden-user wondering why this feature isn’t available. Please implement this! :)

Just adding my voice to the 1600 others. I'll be switching back to Bitwarden until this is resolved. It's a very basic feature and is absolutely needed for anybody self-hosting services.

I run a number of self-hosted VMs on my local network and store passwords in a password manager. Without the ability to do specific domain matching, I get the option to choose from 55 (!!) different logins, since the applications run on the same local domain.

I'm trying to migrate from 1Password to Proton Pass and this is a major inconvenience, as I relied on this functionality pretty significantly in 1Password.

This is such a basic requirement for a password manager that it’s honestly wild it hasn't been implemented yet.

Many of us use different logins for different subdomains, including this very site. Having Proton Pass constantly suggest the wrong account just because the root domain matches is a major headache. "Don't suggest on this site"? No, all blocked. It just doesn't work.

As people start migrating away from Bitwarden, this is going to be a total dealbreaker. It’s not just a power user thing; it’s a core feature in every other manager. Please move this from "under review" to "planned" before more people give up and go back to what they were using before.

1593 votes, since 2023... still nothing? Hopefully this can be added soon. Would make me more willing to switch from Bitwarden

As a few people mentioned, this has been under review for more than a year.

It is essential when self-hosting, and each service has a differente subdomain, but the same domain. Any updates?

This has been "under review" for over a year. The latest Proton roadmap doesn't mention implementation of this feature even though it has over a thousand votes and is a feature that's ubiquitous in major password managers that Proton Pass is meant to compete with.

Is someone from Proton able to speak to why this feature isn't top of the list with regards to Proton Pass enhancements?

As other have mentioned, this makes it very inconvenient to use autofill when self-hosting dozens of services under the same domain names.
Please add the functionality.

Attempted to switch from 1Password and it was disappointing to see that URL matching is not an option. Using subdomains for self-hosted apps made it annoying to have suggested all possible logins for the top domain. No URL matching made this a deal breaker for me.

This would be incredibly useful for me managing my internal server infrastructure. The current setup is, however, better than LastPass who doesn't even allow multiple URLs for one password entry without having to jump through a bunch of hoops.