Introduction

This guide will cover how to utilize embedded link actions within Descope flows. Some common use cases exist where embedded links may be preferred over other authentication methods. One notable use case would be allowing users to verify their email address after they initially signed up and are authenticated to your application rather than verifying the email address during the sign-up process.

Note: While this may enhance your user experience to authenticate faster if utilizing passwords, they will still need to verify their email address before sending a password reset via the normal methods.

This guide will cover the abovementioned use case and the use case for sending password reset via embedded link via flows.

Email Verification After Initial Sign Up

For the use case of allowing a user to verify their email after their initial signup, utilize the embedded link Update User action within your flow. This will require that you have a messaging connector already configured, as you will need a method of sending the embedded link to your user. You can find documentation on configuring connectors within our connectors knowledge base area.

Add the Update User Email Action

Below are other customization options for the embedded link actions that you can make.

• URI: the URL to prepend the embedded link token sent to the user.
• Add to login IDs: This is applicable if you're using phone number or a custom user name as a auth method. To learn more on this option, see our documentation on Associating multiple login IDs for different auth methods.
• Token Expiration allows you to override the configuration within the embedded link authentication configuration page. This is applicable when you want to set different expiration times for different tasks. Email verification for this use case makes sense for 30 days, so 43200; whereas with password reset, you may want to set this to 3 minutes, for example.

Configure Email Sending Action

Add Screens and Connect Flow

Now, you can add a screen showing the user that the email verification link has been sent and another screen stating that the email was successfully verified after the user clicked the link in the email they received.

Test Email Verification

Now that you've added the ability to verify an email after initial sign-up later, you can test the flow. The initial sign-up will continue and give the user a JWT. When they eventually click the link in their email, the user will be authenticated, their email marked as verified and successfully logged in with a JWT.

Password Reset

You would then add another send email action similarly to the above example, and then connect the actions to the applicable screens per the example below.

Other Embedded Link Actions