Outbound Consent Flows

Once you have configured your outbound app, you'll want to allow your users to consent to the scopes you've defined within your outbound app. This guide covers implementing the related outbound consent actions within Descope flows.

Outbound App Flow Components

This section outlines using the Descope outbound app components within your flows.

Generally, you must load the user within the flow before attempting to consent to the outbound application. This can be done via the Load User action within a sub-flow or post-authentication flow. This would be used when you have an area of your application that has an option to Share to YouTube or Share your Google Contacts with us.

You could also prompt users to add consent to additional outbound apps within a general authentication flow to your application. This could even be part of your progressive profiling. For example, if a user returns a second time and authenticates with Google, you could show a screen within the flow, giving the user the option to consent to share their contact information with your application without loading the user.

Outbound App Button

The Outbound App flow component is the button where you would initiate consent to an outbound app.

The Outbound App button can be configured to set the text, select the outbound app you want to use, and style it like other screen and button components. When you select the Outbound App from the drop-down, the button will inherit the logo configured within the outbound app details.

Outbound App Connect Action

The Outbound App / Connect action runs the consent flow with the outbound application. This action can be used in two different ways.

Usage After the Outbound App Flow Button

When used after the Outbound App flow button, you can leave it configured as is, primarily meaning to leave the set a default outbound app unchecked. This will automatically take the input from the flow button and direct the user to the correct outbound app to authenticate. This allows you to create screens with multiple consent options funneling to one outbound app connect action.

Usage Without the Outbound App Flow Button

You may have a scenario where you want to own the buttons within your application that kick off consent to an outbound app. Think of a screen within your application with tiles for Share to YouTube, Share to TikTok, Share to LinkedIn, etc. You could optionally build this within a flow screen like the above example, but let's say that you want to trigger the flow after the user clicks something like one of these buttons within your application without having the user interact with any flow screens.

You can achieve this behavior by using the Outbound App / Connect action, with the checkbox for Set a default outbound app checked and the applicable outbound app selected from the drop-down. With this configuration, once the flow runs, it will immediately load the user and redirect them to the outbound app provider to consent, then return to your application without any Descope screens needing to be displayed.