For Support
What users might ask
"I used 'Logout All Users' but my old phone is still buzzing with notifications." This was the bug this PR fixes. Before the fix, "Logout All Users" ended every session but left each device's push registration in place, so already-logged-out phones kept receiving alerts (appointment booked, invoice created, task assigned, etc.) even though the app itself was locked out. Once this fix ships, clicking "Logout All Users" clears every staff device's notification registration at the same time it ends their sessions.
"Will I stop getting notifications entirely?" Only on the device(s) that were signed out by "Logout All Users." When a staff member logs back in on that device, the app re-registers a fresh push token and notifications resume normally.
"I logged out of just my own account (not 'Logout All Users') — will this affect me?" No. Regular individual sign-out already removed that device's own notification token before this fix. This change is specific to the company-wide "Logout All Users" action.
"What about patients / the patient portal?" Not affected. This fix only touches staff (User) accounts. Patient app/ portal notification tokens are a separate field and this PR doesn't change them.
How to verify/troubleshoot (once released)
- Confirm the report is specifically about **after an owner used "Logout All
Users"** (Settings → Security tab, or the mobile More menu) — not a regular personal logout, which was never affected.
- Have the affected user log back in on the device that's still receiving
notifications. That re-registers the token and should stop any stale alerts.
- If notifications persist after re-login and re-logout, that's outside the
scope of this fix — escalate as a new issue rather than assuming it's a regression of this change.
Where the button lives
Settings → Account → Security tab → "Logout All Users" (owner/Do-All permission only). Mobile: More menu → "Logout All Users." Both call the same backend mutation, so behavior is identical on web and mobile.