Onboard a New Organization with Portal Integration Configuration
When a new HLF organization is provisioned on the platform, the global administrator works through a portal integration setup checklist in the admin portal. This covers: setting initial feature ownership flags based on the organization's current portal maturity, configuring deep link URLs for the organization's Min Side instance, and registering the organization's webhook source identifier so that inbound payloads from their Dynamics installation are correctly routed. The portal integration repository stores all of this configuration under the organization's context. The global admin can use a default template to pre-populate settings and then customize per organization.
User Story
Acceptance Criteria
- Given a global admin is onboarding a new organization, when they open the portal integration setup for that organization, then all configuration fields start pre-populated from the platform default template
- Given a global admin customizes the feature ownership flags for the new organization, when they save the configuration, then those flags apply only to that organization and do not affect other organizations' configurations
- Given a global admin enters the organization's webhook source identifier, when a Dynamics webhook payload from that organization arrives, then the infrastructure correctly routes and scopes it to that organization's data context
- Given the onboarding configuration is complete, when the global admin marks the portal integration as active, then the organization's app users begin receiving portal-synced data and feature ownership flags take effect
- Given a global admin wants to replicate one organization's portal configuration to another, when they use the copy-configuration function, then all flags, URLs, and identifiers are duplicated to the target organization for further customization
Business Value
Each HLF organization may have a different Min Side portal setup, feature rollout timeline, and Dynamics installation. Without a structured onboarding configuration path, global admins must configure each organization through fragmented settings screens and risk inconsistent or incomplete setup. A unified onboarding workflow reduces configuration errors, shortens the time to go-live for new organizations, and ensures portal integration is correctly scoped from the start rather than retrofitted after issues emerge.
Components
- Portal Integration Config Screen ui
- Portal Sync Service service
- Portal Integration Repository data
- Portal Webhook Infrastructure infrastructure