External Portal Integration

HLF is actively redesigning its Dynamics-based member portal and has explicitly flagged that the Meander app and that portal must not overlap or work against each other. Without a formal integration layer, organizations risk confusing users with redundant surfaces, inconsistent data, and conflicting workflows - all of which erode trust and adoption. This feature protects the platform's commercial relationship with HLF by demonstrating that Meander is a good citizen in an existing ecosystem rather than a replacement forced on reluctant users. It also signals to other prospective organizations that Meander can coexist with their existing tooling, which is a direct sales advantage. Coordinated portals reduce support costs, prevent data divergence, and give administrators a single configuration point rather than two disconnected systems to maintain.

The integration is implemented as a configurable connector service in the admin portal backend. A secure webhook or polling endpoint receives events from the external portal (e.g. membership updates, role changes) and maps them to Meander's internal user and organization model via a schema translation layer. The admin UI exposes a Portal Integration Config Page where per-organization connection credentials, field mappings, and sync frequency are managed. All credentials are stored encrypted and never exposed to the client. The connector is deliberately read-oriented at MVP - it ingests data from the external portal but does not write back, avoiding circular update loops. OAuth 2.0 or API-key authentication is used depending on what the external portal supports. Integration health and sync logs are surfaced in the admin portal so administrators can diagnose failures without engineering involvement.