Better Auth account identity map
Same rows. A different key. See what comes together in 1.7.3.
Synthetic demonstration · 3 rows
Inspect the connection.
Choose a row to follow its identifiers.
Only supplied rows are inspected.
Loading the map…
Understanding the atlas Keys, rows, people ↗
Read the connections before changing the data.
A central circle is one lookup key. The surrounding circles are the account rows with that exact key. Switch between issuer and provider contracts to regroup the same records; the tool never changes those records.
Start with the three-row example: two issuers identify different people, then meet at one provider key. The second example shows why duplicate rows are still ambiguous when their user labels match. The third leaves absent issuers unknown.
Before acting on a finding, establish which account schema your deployment actually used. A clear projection can coexist with a remaining NOT NULL issuer column that rejects the next insert. Those are separate observations and separate checks.
Local input, bounded claims. This map compares exact strings in your projection. It cannot see missing database rows, collations, provider ownership or live sign-in behavior. See the real-version tests and exclusions.
After the data review, verify an old and a new account in your own staging app. The map alone cannot establish that either flow works.