Coordinator Proxy Reporting

Three of four organizations - NHF, HLF, and Barnekreftforeningen - explicitly identified proxy reporting as a required capability, making it one of the most broadly validated non-universal features in the platform. Without it, coordinators are forced to maintain parallel manual records for peer mentors who cannot or will not self-report, which directly defeats the platform's core goal of eliminating manual Excel aggregation and underreporting. The feature also protects Bufdir reporting accuracy, since activity counts are per peer mentor and any gap in proxy coverage would result in undercounting. Strategically, enabling proxy reporting allows organizations to onboard the platform incrementally - digitally confident peer mentors self-report while coordinators carry the remainder - reducing the hard-cut risk that all four organizations explicitly flagged as unacceptable.

The coordinator must be able to select a peer mentor from their managed roster as the activity subject before filling in the activity form. The resulting activity record is stored with the peer mentor's user ID as owner and the coordinator's user ID as submitter, supporting auditability. Role guard must verify the coordinator belongs to the same organization and has management rights over the selected peer mentor. The API endpoint for proxy submission must accept an explicit `on_behalf_of` user ID and validate it against the coordinator's org membership. On the mobile side, the proxy flow branches from the standard activity wizard: a role-switch-style peer mentor picker is inserted before the contact/date step. Offline support must queue proxy submissions in the mutation outbox with the target user ID preserved, as the sync resolver needs it to assign the record correctly on upload.