Skip to main content
This is the standard use case delivered by the Update Notification Channel Process. An authenticated user selects to change their primary notification channel. The client does not specify the target authN ID (i.e., the desired new notification channel), so the Process will instead calculate which authN IDs are applicable, and then return an indexed list of options for the user. This Process is designed to return the minimum required information (i.e., the current user’s applicable authN ID options) to the client, if a target authN ID is not specified upfront. You can also see the “single step” use case wherein the client first collects a target authN ID and supplies to the Process it in the initial request.

Initial Request

Your client calls the Process Start API to initialize the Process:

Response: prompt to specify authN ID

Storefront Gateway looks up all of the current user’s email addresses and mobile numbers that are registered as an authN ID with an activated status. The Process then returns an indexed set of applicable authN IDs (taken from the current User entity’s emails and mobiles objects). The response includes a prompt to specify the target ID by their corresponding index number:

Final Request

The user selects their desired authN ID, and your client passes that choice to Storefront Gateway in a Process Step API request:

Process Complete

Storefront Gateway sets authN ID (that was specified by the index number) as the user’s primary notification channel. All system-generated notification messages for that user will now be sent to that channel. The Process ends and returns an HTTP 200 status:
Parent topic:Update Notification Channel Process