+1, not switching from Bitwarden until this feature exists. I have multiple apps running under my domain and matching to subdomain is critical for me.

I'd love to see this feature!
I selfhost a bunch of apps under the same root-domain.
It's annoying to see all available logins for my root-domain with Proto Pass. In Bitwarden resp. Vaultwarden I am able to change the URL detection to "host".

I would love to switch to Proton Pass but I won't be able to until this feature is added. I self-host a lot of apps and use different passwords on each app and its subdomain. Bitwardens matching allows me to use "Starts With" matching which will only show the correct password on each subdomain. Right now Proton pass shows all 10 mixed together.

Had to go back using bitwarden while waiting for this feature to be added, protonpass looks better ui/ux but this is really one of the missing feature to be able to use it correctly on subdomain and exact url match.

Same here. When there are a lot of subdomains or shared domains, it is a pain not to have this feature :)

I won't switch to Proton Pass without this feature. Absolutely mandatory. I'm staying with Bitwarden.

I'm slowly coming around to the way Proton Pass does URL matching with URLs included on each password entry versus the global URL matching that LastPass does.

Regardless of whether Proton Pass continues having URLs managed in individual password entries or globally at some point, each URL entry should have a way to configure how it will match. I hope to see options for:
- "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

Allowing regular expressions with these options would make an incredibly powerful and flexible way for users to control when matches are offered.

Also waiting this feature…
I am in the same use case both, for work and for personal.

This is massive and the primary reason I am not using ProtonPass yet.

Create option(s) where an username/password should be used (or not be used) based on arguments like:
base domain; exact match; regular expression

and more