Subject: Proton Pass struggles with multiple Workday (SaaS) tenants on same domain

Hi,

When working with SaaS solutions like Workday, Proton Pass has trouble handling multiple accounts that live on the same base domain.

Example:
- https://simcorp.wd3.myworkdayjobs.com/
- https://ag.wd3.myworkdayjobs.com/

Each of these URLs belongs to a different company tenant, but they all share the common base domain “myworkdayjobs.com”.

The problem:
When I create a new login for a different Workday tenant, Proton Pass suggests updating an existing entry instead of creating a new one. It appears to match only on the common domain “myworkdayjobs.com” rather than recognizing the full subdomain (e.g. simcorp.wd3.myworkdayjobs.com vs ag.wd3.myworkdayjobs.com).

Current workaround:
To distinguish between the entries, I have to put the company name in the username field or in the item title, which is not ideal and does not reflect the actual username.

Feature request:
Could you:
1) Improve matching so Proton Pass can treat different subdomains on the same SaaS domain as separate sites, and/or
2) Provide an option to force Proton Pass to create a new login entry even when the base domain matches an existing one?

This change would make Proton Pass much easier to use with multi-tenant SaaS platforms like Workday.

Best regards,
Jesper

i've been using proton for almost 2 years now. i have seen this issue a long time ago already and its still not implemented... i think this one is a deal breaker. how is it still not a thing

At the very least proton pass should be able to differentiate between subdomains.

This is a must have - considering going back to bitwarden. But otherwise Protonpass is excellent!

Any news on this?

UP Please, i really need this for my business...

Why isn't this fixed yet? This should have been in version 0.001 alpha.

God, nearly 3 years later, still not there... I'm not a developer, but is this so complex to implement, I mean, filtering the passwords by the full URL instead of the main domain only should be basic no?

Agreeing with @Nick. I was close to pulling the trigger on purchasing a Proton Premium subscription, but the lack of this specific feature is holding me back and keeping me on Bitwarden for now.

Ready to purchase as soon as this is a feature. Even just a partial implementation of hostname matching would be huge. During my testing I get 40+ login options each time I visit something in my homelab :(

And do not forget to match per port as well!

I think that pattern matching (wildcards, regular expressions) would be very convenient.

One of the main reasons why I cannot switch from 1password.

We need absolutely this feature ! @Proton, come on please ! 🙏

I regret the move from Dashlane to Proton. This one is extremely annoying

This is actually a blocker for me to move from Bitwarden to ProtonPass

Comment for Proton Pass Feedback Thread (“Domain URL Matching Rules”)

As an active Proton ecosystem user running a self-hosted domain (e.g. example.net), I can confirm that the current substring-based URL matching in Proton Pass severely limits usability for anyone who uses their own domain for both email and internal services.

Example:
All of my logins use @example.net as the username, and I host services like
nextcloud.example.net, grafana.example.net, and truenas.example.net.
When I visit any of those sites, Proton Pass lists every vault item containing “example.net” anywhere in the record — dozens of unrelated logins — instead of only the one matching subdomain. This makes the extension nearly unusable for homelab or enterprise setups.

What’s needed:
Proton Pass should implement configurable domain-matching rules, just like Bitwarden and 1Password:

Exact host match (grafana.example.net)

Base domain match (*.example.net)

Starts-with / wildcard (service*.example.net)

Regex (for advanced users)

Multiple URLs per credential

This would allow Proton Pass to support professional and self-hosted use cases while maintaining strict security boundaries between services. It’s also essential for organizations that share a common apex domain across many logins.

Until Proton supports per-entry match modes, anyone with a homelab or corporate domain faces an autofill list so long it borders on unusable.

“Let all things be done decently and in order.” — 1 Corinthians 14:40, KJV
Precise domain matching is the digital equivalent of order. Please prioritize this improvement soon.

— A long-time Proton user and self-hoster

Baffled this isn't already a feature. I'm finding posts about this (and CS responses) from over 2 years ago.

I come from keepass and this is a must have. Without more flexible matching rules I see too many accounts for a given domain and picking the correct one is a pain.

Same as Justin below, I also have a home lab and tons of services, each with different logins. Having a way to match urls would be really useful

Adding my vote. This is a really important feature for professionals and home labbers. Without a "starts with" or similar rule, you can have dozens of accounts show up for everything under a domain.