I manage hundreds if not thousands of systems that are all located under a few domains, ie system1.domain.com, system2.domain.com, system3.domain.com etc.
This makes Brave basically unusable since it considers every system to be one and the same when it comes to autofill information and saved logins. If I login to system99 or whatever and ask it to save the password, it will update the password for all of the hundreds of sites I have under the same domain.
I can understand the idea behind this and I accept that it’s common that every site under the same domain uses the same login. It is however not always the case, and assuming so is actually a security risk.
Would it be possible to make this behavior optional with a simple “do not consider subdomains to be related” or similar setting?
Or better yet, a conditional option where you could list domains under which subdomains should not be considered related?
This is obviously a Chromium upstream issue, you need to ask Chromium developers to fix that, because there is NOT a Chromium browser that fill passwords per subdomain, no Fork is going to waste time “fixing” this, only because you have to login in a lot of subdomains which is rare for 99% of people.
Maybe a password manager extension will do what you want, so try them.
For example in Chromium 115, or maybe even 114 there are some Chromium flags to use Notes in Brave’s password manager, but to even even use the new Chromium password manager inside Brave, but it has a Grouping feature and as you can see, Chromium just cares about domains, so this is why I said you should request Chromium team to change it.
I’m having a related issue. Several of the medical websites in my area are using a common domain for signon, so I can’t use brave for the passwords for those sites. It would be nice if you could tell brave that “https://sso.ema.md/” actually has multiple passwords and it should let me pick the one I need to use. All these sites use my email as login, otherwise I could try to change my login for the different sites.
Also I did read the reply to the original post and see anon57… says this is inherited behavior from the chromium browser. If I find where to post bugs for that I will do so.
I rewrote your issue, and entered the following at Perplexity.ai >
“Several of the medical websites in my area are using a common domain for signon, so I cannot use the Brave Browser Password Manager for access to those sites. Might Proton Pass be good for this situation?”
Answer at Perplexity.ai (https://www.perplexity.ai) >
Yes, Proton Pass should work well for that situation, and it will also avoid the “one password per domain” limitation you’re running into with Brave’s built‑in manager.
Why Brave’s manager struggles
Brave’s password manager generally treats all subdomains under the same parent domain as one site (for example, clinic.healthsystem.com and portal.healthsystem.com get one shared login). That means if your different medical portals all authenticate via a shared domain, Brave will keep overwriting the saved credentials instead of storing separate ones.
How Proton Pass helps
Proton Pass is a standalone password manager that:
Stores logins independent of the browser, with separate entries for each account even if sites share a domain, as long as you save them as distinct items.
Offers browser extensions (including for Chromium‑based browsers like Brave), so you can still autofill while bypassing Brave’s built‑in password logic.
Syncs across devices, so your credentials are available on desktop, mobile apps, and other browsers if you ever switch.
Practical setup for your case
Turn off (or stop using) Brave’s own password saving and rely on Proton Pass via its extension in Brave.
In Proton Pass, create a separate login item for each medical site; if Proton Pass tries to match them too broadly, you can edit the URL/website field so each item is tied to its specific login page.
Test autofill on each portal; if one is finicky, you can always copy‑paste from Proton Pass instead of using autofill.
Alternatives and considerations
Any reputable third‑party manager (Bitwarden, 1Password, etc.) would also avoid Brave’s domain‑wide behavior and give you per‑site or per‑URL control.
Proton Pass has a strong free tier with unlimited devices and entries, plus extras like built‑in 2FA codes and email aliases on paid plans if you want more privacy features later.
Yet, I would make sure to use the combination of: a unique Username and unique Password per sub-domain. And test that for Brave’s Password Manager, in addition to alternatives like Proton Pass and 1Password.
Also, at some websites, I have to manually enter the unique Username . . . and then the password manager (aka password wallet) will submit the matching unique Password.
