Only using the root domain is actually an issue as well. E.g. I have two completely different sites I need to log in to, but they both share .zendesk.com as the root domain.
Ideally We would be able to toggle on the pass record if it should use the complete URL for login filtering, or if it can rely solely on the root domain.

ideally please add the little drop down for autofill behaviour like in 1Password where you can set to fill on that TLD, that specific host (subdomain and/or port specific), or never autofill, it's a small feature but one that is much needed

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

Please include this as I am tired of either the credentials not popping up because the subdomain or port number is not included in the URL of the saved credentials OR constantly being asked for credentials even though the root domain already asked me for it.

Please add Regular Expression support! I won't be moving over from Bitwarden until this is added.

> website entered in Proton Pass as xyz.com will still autofill at accounts.xyz.com, and not ask to save 'new login'

Maybe form autofill should be initiated by user (ideally using single tap/click of the mouse), not done automatically upon loading ANY webpage that has a webform, due to claimed possibility of malicious Javascript capture autofilled data, says Robb Braxman: https://youtu.be/spSdUSgAkKg?si=Ly2rEl5A681josoF&t=401

This should be the default behavior! Only require configuring a rule if different behavior is desired for different subdomains.

That would be better to include matching rules on URLs.
That would answer multiple use cases and not just this specific one.

https://protonmail.uservoice.com/forums/953584-proton-pass/suggestions/47012971-domains-url-matching-rules

For my professional daily job, I use to switch between several servers onto the same root domain.
Having an address such as `https://*.mydomain.tld` should help to reduce credentials noises.

Proton Pass simply needs URL matching rules like Bitwarden has.

Sometimes you need different logins for subdomains, sometimes you don't. Rules that determine what part of the URL to match on (including a regular expression) would be great.

This feature need also the option to mark domains as 'no route domain'.
There are services that need a separate account per sub-domain, like uservoice.com