- Ya
- 21 Agosti 2026, 03:34 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 1a5c213
POST **************** now honours onBehalfOfMemberId, gated on EDIT_OPPORTUNITIES — the right that gates managing opportunities on the reserved list, and already the right needed to move an opportunity between agents after the fact. CREATE_OPPORTUNITIES alone still only files your own. A caller without it that names an agent is REFUSED rather than having the field dropped. Silently recording the reservation under their own name would attribute a claim to somebody who never made it, and would show the manager a request they believe they filed for someone else. The named agent is validated against commissionEligibleMemberIds — the same VIEW_LEADS pool applyPrimaryAgent uses and the same pool the picker offers. Parking a reservation on somebody who cannot open the lead it reserves is unworkable for them. The history row's actor stays the person who acted; the note says who it was for. And because REQUEST_SUBMITTED goes to approvers, the agent it was filed for is added explicitly — they are not an approver, so otherwise the first they would hear of a claim in their name is its approval or denial. Requires the KamoInitializerService migration adding CREATED_BY_MEMBER_ID to have run first, or the first read of any reservation throws.