# Brave password manager combines 2 sites

**URL:** <https://community.brave.app/t/brave-password-manager-combines-2-sites/660256>\
**Category:** Desktop Support\
**Tags:** windows\
**Created:** [October 26, 2026, 4:35pm UTC](https://community.brave.app/t/brave-password-manager-combines-2-sites/660256 "2026-10-26T16:35:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jarno21](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@jarno21](https://community.brave.app/u/jarno21)\
**Post date:** [October 26, 2026, 4:35pm UTC](https://community.brave.app/t/brave-password-manager-combines-2-sites/660256/1 "2026-10-26T16:35:23Z")

</div>

For some reason, the brave password manager combines together 2 site passwords. The sites are part of the same company managed domain. Due to this combination, changing the password on one site and saving it leads to me being unable to autofill the password on the other site. Brave version 1.98.60

---

<div class="post-metadata">

**Author:** ![289wk](https://avatars.discourse-cdn.com/v4/letter/2/439d5e/32.png) [@289wk](https://community.brave.app/u/289wk)\
**Post date:** [October 31, 2026, 4:50am UTC](https://community.brave.app/t/brave-password-manager-combines-2-sites/660256/2 "2026-10-31T04:50:34Z")

</div>

@jarno21

This is a well-known **Chromium upstream behavior** :

> The password manager treats all subdomains under the same parent domain as a single site.

There’s an older thread ([Manage different logins/passwords for subdomains under the same domain](https://community.brave.app/t/manage-different-logins-passwords-for-subdomains-under-the-same-domain/495004) July 2023)

… where the response is essentially:

> This is inherited from Chromium; no fork is going to “fix” it; and the workaround is to use a third-party password manager (Bitwarden, 1Password, Proton Pass, etc.) or ensure each subdomain uses a **unique username** so Brave stores them as separate entries.