high complexity extracted Organization Structure & Multi-Tenancy Confidence: 100%
4
Components
58
Shared
0
User Stories
Yes
Analyzed

Description

This feature provides integration adapters connecting the platform to external systems used by partner organizations: HLF's Dynamics-based member portal, Xledger accounting system (Blindeforbundet), Cornerstone learning management system, and Consio. Each integration handles data synchronization, single sign-on federation, or financial data export depending on the external system's capabilities and the organization's requirements. The integration layer is designed to be adapter-based so new external systems can be added without modifying core business logic.

User Flow

External Portal & Accounting System Integration user flow
Click to expand

Analysis

Business Value

HLF has an explicit contractual requirement that the mobile app must not conflict or overlap with their ongoing Dynamics portal redesign — both systems must coexist and ideally share data. Xledger integration for Blindeforbundet automates the export of approved reimbursements directly into the accounting system, eliminating manual re-entry and associated errors. Cornerstone integration enables course enrollment data to flow automatically without administrators maintaining two systems. These integrations are the primary mechanism by which the platform embeds itself into each organization's existing toolchain, increasing switching costs and long-term retention. Without them, organizations must maintain double data entry, which erodes the platform's value proposition over time.

Implementation Notes

Each integration is implemented as an isolated adapter class behind a common IntegrationAdapter interface, registered per organization in the integrations table. HLF Dynamics integration uses OAuth2 with the Dynamics 365 REST API for user and membership sync. Xledger integration uses their SOAP or REST API for expense record export after reimbursement approval. Cornerstone and Consio integrations are lower priority and may use CSV export as an initial implementation if API access is unavailable. The Next.js backend handles all outbound integration calls server-side to avoid exposing third-party credentials to the mobile client. Integration settings are configurable per organization from the admin panel, including API keys, endpoint URLs, and sync schedules. Webhook receivers handle inbound events where supported.

Components (62)

User Interface (1)

Service Layer (1)

Data Layer (1)

Infrastructure (1)

Shared Components

These components are reused across multiple features

Infrastructure (20)

User Stories

No user stories have been generated for this feature yet.