External Portal Integration

HLF has an active parallel portal project on Microsoft Dynamics and has explicitly flagged that the Meander app and the Dynamics portal must not overlap or work against each other. Without a structured integration layer, HLF risks data fragmentation, duplicate membership records, and confused users who see inconsistent information across two systems. Delivering this feature is a condition for HLF's full adoption of Meander. It also demonstrates the platform's openness to coexistence with existing organizational infrastructure - a significant commercial message for other prospects who have incumbent systems they cannot immediately retire, consistent with the incremental rollout principle (§1.5).

Integration configuration is persisted in the organizations table as a config flag (not a separate area toggle) per the guideline that a config flag inside an area is preferred over a new area when only one tenant dimension varies. An ExternalPortalApiClient handles outbound HTTP calls to the registered endpoint using organization-scoped credentials stored in a secrets store (not in the main database). The ExternalPortalSyncService implements configurable field-level authority rules (which system owns which data domain) and handles conflict resolution on sync. Initial implementation targets read-only sync (Meander pulls membership and role data from the external portal); write-back is a later enhancement. API client uses exponential backoff and records sync results in the audit log.