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