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

User Story

As a administrator
I want to toggle which app features are designated as app-owned versus portal-owned for my organization
So that So that users experience a coherent, non-overlapping journey across the Likeperson app and HLF's Min Side portal without encountering duplicate forms or conflicting data entry points

Acceptance Criteria

  • Given an administrator is on the portal integration config screen, when they toggle a feature flag from 'app-owned' to 'portal-owned', then that feature is immediately hidden from the app UI and replaced with a deep link to the configured portal URL
  • Given a feature is flagged as 'portal-owned', when a user navigates to that section of the app, then they see a clear handoff card with a button linking to the Min Side portal — not a disabled button or error
  • Given an org admin saves a feature ownership configuration, when another user in that organization opens the app, then the updated ownership flags are reflected within one sync cycle
  • Given a global admin is configuring the platform, when they view the portal integration config screen for any organization, then they can read and modify that organization's feature ownership flags
  • Given the config screen loads, when the administrator views it, then all toggleable feature categories are listed with their current ownership status (app or portal) clearly indicated

Business Value

HLF is concurrently redesigning its Dynamics portal, creating a real risk of feature duplication that wastes development effort and confuses volunteers who must decide which system to use for a given task. Explicit feature ownership flags eliminate this ambiguity at the configuration level, protecting HLF's investment in both platforms and enabling a coordinated rollout strategy where features can be migrated between systems without requiring app releases.