Skip to main content
In terms of the client expectation, this API flow is identical to the Existing User use case. So you can consult that topic for the full API walk-through. The only difference with this scenario is that the invitee is not currently a registered Storefront Gateway User. Therefore, this Process creates a new Storefront Gateway User entity with an activating status on the back end. When the Process successfully completes, the invitee receives an invitation message and clickable link just like in the previous scenario. However, the Storefront Gateway Action Token is context aware so that the subsequentAccept or Decline Process will correctly prompt the invitee finish their user onboarding (i.e., to set a password) before they access any of the shared services. Parent topic:Share Access to an Account, Subscription, or Feature