Skip to main content
This use case is similar to the “New user accepts invite” scenario. One user invites another user to share access to one of their associated accounts or services. The client application for the service uses the Share Access to an Account/Subscription/Feature Process. At the end of that Process, Storefront Gateway sends an invitation to the invitee’s email or mobile number (whichever the inviting user provided to the previous Process). The invitee then uses that link to redirect to the application, and explicitly accepts the invitation. In this scenario, the invitee is already an existing (i.e., fully onboarded and activated) Storefront Gateway User.

Initial Request

The invitee clicks the invitation link, which then redirects them back to a dedicated landing page in your application. Your client takes the action token value directly from the redirect URL, and calls the Session Token API with the token value as a URL parameter. This initializes the Process:

Response: Accept or Decline

Storefront Gateway responds with a prompt for the user to explicitly accept or decline the invitation:

Final Request: User Accepts

The user explicitly accepts, and your client passes this choice back to the Process through the Process Step API:

Process Complete

The Process activates the following:
  • The association(s) between the invitee’s User entity and the shared account, subscription, or feature entity (or entities).
  • The association between the invitee’s User entity and the Group entity (if the invitee was not already a Group member)
The Process then authenticates the current user, and returns a 200 HTTP status code:
The current user now has access to any of the accounts/services that were shared with them by the inviting user.