🏠 Overview › 👥 User Roles ›📖 Receive and Apply Membership Updates Synced from M...

Receive and Apply Membership Updates Synced from Min Side Portal

When HLF administrators update membership records in the Min Side Dynamics portal, the portal publishes a webhook event to the Likeperson app's webhook endpoint. The portal webhook infrastructure validates the payload signature and enqueues it; the portal sync service then processes the event and updates the relevant Supabase records — user profiles, organization memberships, or role assignments — according to the event type. The organization administrator can verify that a recently made portal-side change has propagated by checking the sync log in the portal integration config screen.

HIGH story-external-portal-coordination-organization-administrator-006 8 pts
8
Story Points
High
Priority
External Portal Coordination
Feature

User Story

As a Organization Administrator
I want membership changes made in the HLF Min Side Dynamics portal (such as new members, role changes, and deactivations) to be automatically reflected in the Likeperson app without manual re-entry
So that So that coordinators always work with current membership data and I do not need to duplicate administrative changes across two separate systems

Acceptance Criteria

  • Given a new member is added in the Min Side portal, when the portal publishes the membership-created webhook event, then within two minutes the new member's profile is available in the Likeperson app under the correct organization
  • Given a member's role is changed in the Min Side portal, when the role-updated webhook event is processed, then the member's access level in the Likeperson app reflects the updated role on their next app session
  • Given a member is deactivated in the Min Side portal, when the membership-deactivated webhook event is processed, then the member can no longer access the Likeperson app and is marked inactive in coordinator views
  • Given an organization administrator views the sync log after making a portal-side membership change, when the event has been processed, then the log entry shows the event type, timestamp, and 'success' status
  • Given the portal sync service receives a membership update event for a user that does not exist in the app database, when it processes the event, then it creates the user record rather than failing, and logs the creation

Business Value

HLF's membership source of truth is the Min Side Dynamics portal. Without automated sync, organization administrators must manually replicate every membership change into the Likeperson app — a time-consuming, error-prone process that guarantees eventual data divergence. Automated sync eliminates the double-entry burden, ensures coordinators have accurate member information, and removes the risk of peer mentors retaining app access after being deactivated in the portal.

Components

External Portal Coordination
Related Feature
Organization Administrator
User Role