Configure Deep Link URLs for Portal Handoff Navigation
The portal integration config screen includes a deep link management section where administrators can define and update URL mappings between app feature contexts and corresponding portal destinations. These mappings are stored in the portal integration repository and used at runtime by the app to construct handoff links. Organization administrators configure their own organization's deep links; global administrators can configure defaults and override mappings for any organization during onboarding or troubleshooting.
User Story
Acceptance Criteria
- Given an administrator opens the portal integration config screen, when they navigate to the deep link configuration section, then they see a list of configurable link mappings with their current URL values
- Given an administrator enters a new deep link URL for a portal-owned feature, when they save the configuration, then the app immediately uses that URL for all future handoff navigation from that feature context
- Given a configured deep link is triggered in the app, when the user taps the handoff button, then the portal URL opens in the device browser with any required context parameters appended
- Given a deep link URL field is empty, when the administrator tries to save, then validation prevents saving and displays a required field error
- Given a global admin is onboarding a new organization, when they configure default deep links for that organization, then those URLs are applied until overridden by the organization administrator
Business Value
Deep links that route users to the correct portal destination remove a critical navigation pain point in cross-platform journeys. Without them, users redirected to the portal homepage must re-navigate to their task, leading to drop-off and the erroneous conclusion that the integration is broken. Correct deep links are a prerequisite for the portal coordination feature to deliver any user experience value.