Who should see what in the response workflow
Access levels across survivor, responder, specialist, and admin workflows.
Survivor and community users
People who submit reports should be able to see their own report status, emergency actions, trusted contacts, and survivor-facing progress language without inheriting responder detail.
Operational specialists
NGO, police, counselor, legal, medical, and shelter roles should see the assignments and case detail necessary for their lane, not the full universe of case information by default.
Admin and governance roles
Admin should oversee queue health, verification, closure governance, and compliance boundaries rather than acting as the default frontline handler for all cases.
Visibility principles
Operational access boundaries across the workflow.
- Initial access should be bounded by the assigned role, coordinator status, and verified operational need.
- A specialist should see assignment reason, closure impact, and relevant timeline context, but not unrelated partner-only data outside that lane.
- Admin access should expand around governance checks, organization verification, and closure review rather than unrestricted case handling.
- Public data surfaces should never expose raw case detail, named survivors, or re-identifiable low-volume combinations of facts.
Current role model
Coordinator and specialist access patterns.
Coordinator roles
NGO and Police should own most coordination depending on severity, enforcement need, fatality status, and intake pathway. They dispatch, review readiness, and carry primary case ownership.
Specialist roles
Counselor, Legal Aid, Medical Provider, and Shelter Operator should work from assigned queues with explicit assignment intent and closure impact rather than acting as implicit coordinators.