External Portal Integration
Feature Detail
Description
This feature enables the Admin Web Portal to connect with HLF's external Dynamics-based member portal, ensuring the two platforms operate in sync rather than in conflict. The integration surfaces configuration options in the admin portal so that organization admins can manage connection settings, API credentials, and data-sharing rules without developer involvement. The goal is to prevent data duplication and functional overlap between Meander and the external portal while keeping member-facing information consistent across both systems.
User Flow
Analysis
HLF is actively redesigning its 'Min Side' on the Dynamics platform and has explicitly flagged that the Meander app and its portal must not overlap or undermine each other. Without a formal integration layer, organisations risk dual data entry, conflicting user records, and member confusion. Providing a managed integration reduces administrative overhead, prevents data inconsistencies, and protects Meander's credibility with multi-portal organisations. Strategically, this capability broadens Meander's appeal to larger organisations that already operate their own portals, making Meander a complementary rather than competing tool and unlocking enterprise sales opportunities.
The integration should be implemented as an adapter pattern behind an abstract ExternalPortalService interface so that future portals (beyond Dynamics) can be added without touching core logic. The admin-facing settings page stores encrypted API credentials in the database using envelope encryption. Data synchronisation should be event-driven via webhooks where the external portal supports it, falling back to scheduled polling. A Portal Adapter infrastructure component handles protocol translation and error normalisation. All sync operations must be idempotent and logged to the audit log. Failure modes must be handled gracefully: failed syncs queue for retry and surface actionable alerts in the security dashboard rather than silently dropping data.
Components (119)
Shared Components
These components are reused across multiple features
User Interface (12)
Service Layer (34)
Data Layer (22)
Infrastructure (38)
User Stories
No user stories have been generated for this feature yet.