You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported during QA session. Future enhancement — not scheduled.
What's wrong
The map is rescuer-only. app/(drawer)/(tabs)/map.tsx gates on useAuth().isRescuer and redirects everyone else away, so an ordinary authenticated user in an emergency has no way to see whether help is nearby or where it is.
What I'd like
An authenticated non-rescuer should be able to open the map and see rescuers only — never other regular users. The rescuer-visible view (all users, including people needing help) stays rescuer-only.
Proposed change
Relax the mobile map's isRescuer gate to allow any authenticated user in, with a role-dependent dataset.
Enforce the filtering server-side. The endpoint backing the map (server/app/api/gps.py latest-locations / the GPS WS) must return only rescuer positions to a non-rescuer caller. Client-side filtering alone is not acceptable here — it would ship every user's live coordinates to every device and just hide them in the UI.
Suppress rescuer-only affordances for non-rescuers (location history/path playback, and anything else that exposes a specific person's movement over time).
Should a non-rescuer see all rescuers, or only rescuers within some radius / assigned to their incident? Broadcasting every responder's live position to every account is a real disclosure decision, not just a filter.
Should a non-rescuer's own position be published to rescuers as a side effect of opening the map, and is that consented to anywhere today?
Does rescuer presence/availability status need to be exposed too, or position only?
Additional context
This touches who can see whose live location, so it needs a security review before implementation, not after. Depends on #322 (rescuer marker differentiation) landing first to be useful. Related: #324 (admin-published map sites) — same goal of making the map useful to non-rescuers.
Reported during QA session. Future enhancement — not scheduled.
What's wrong
The map is rescuer-only.
app/(drawer)/(tabs)/map.tsxgates onuseAuth().isRescuerand redirects everyone else away, so an ordinary authenticated user in an emergency has no way to see whether help is nearby or where it is.What I'd like
An authenticated non-rescuer should be able to open the map and see rescuers only — never other regular users. The rescuer-visible view (all users, including people needing help) stays rescuer-only.
Proposed change
isRescuergate to allow any authenticated user in, with a role-dependent dataset.server/app/api/gps.pylatest-locations / the GPS WS) must return only rescuer positions to a non-rescuer caller. Client-side filtering alone is not acceptable here — it would ship every user's live coordinates to every device and just hide them in the UI.Open questions
Additional context
This touches who can see whose live location, so it needs a security review before implementation, not after. Depends on #322 (rescuer marker differentiation) landing first to be useful. Related: #324 (admin-published map sites) — same goal of making the map useful to non-rescuers.