Dentolize · Regional DB Split Walkthrough
On this pageWhat users might notice and ask aboutWhat did NOT changeAdmin-side (internal staff) changesWhen to escalate to engineering

For Support

What users might notice and ask about

  • "I added a second account and now I see two avatars in my profile menu — is that normal?" Yes. This is the new multi-account switcher. Users can hold multiple logins (their own account plus, say, another clinic's, or another staff member's) and switch between them from the profile menu without logging out. See the Walkthrough screenshots. If a user didn't intend to add a second account, they can remove it from the same menu, or just log out of it.
  • "Login feels like it takes an extra beat before the form even responds." Expected — every login now does a region lookup first (asking "which server does this account live on") before the password is even checked. It should still be well under a second; if it's visibly slow or hangs, that's worth escalating, since it may indicate the Auth Server or a regional API is unhealthy.
  • "I logged out but I'm still logged in as someone else." Also expected, if the user had more than one account stored. Logging out of the current account falls back to the next stored account automatically rather than always dropping to the login screen. To fully sign out of everything, they need to remove/log out of each stored account individually.
  • A public link (patient timeline, QR code, shared invoice) doesn't load, or loads the wrong thing. These links now carry a small encoded hint pointing at the right region. If the hint is missing or stale (an old link, generated before this rollout, or copied incorrectly), the app falls back to a slower lookup and — if that also fails — proceeds with whatever region is currently active in the browser, which may be wrong. Ask for the exact link and check whether it has a ?c=... parameter.

What did NOT change

Patient records, appointments, invoicing, insurance claims, inventory, WhatsApp messaging, and all other day-to-day clinic workflows are functionally identical. If a user reports something broken in one of those areas, it's very unlikely to be related to this PR — troubleshoot it normally.

Admin-side (internal staff) changes

If you're supporting a Dentolize admin (not a clinic user): the Cron Jobs screen in the internal admin dashboard now requires picking a Region from a dropdown before cron status or Redis tools will show data — if an admin says "the cron jobs page is empty," check whether they've selected a region.

When to escalate to engineering

  • Any report of seeing another clinic's data, or a login resolving to the wrong region — this would be a serious isolation bug given the whole point of this PR is regional data separation.
  • Any failure during an active company-region migration (a clinic reported as "temporarily disabled" mid-move is normal and expected during a migration window; a clinic stuck disabled with no active migration is not).
  • Repeated "company not found" errors on the clinic-login-name login flow for a clinic that should exist — could indicate a stale or missing routing mapping.