Unable to Resend Confirmation Email to Unverified Users due to Lack of Email Access

[SergejSi]

Link
https://supabase.com/docs/reference/javascript/auth-resend?queryGroups=example&example=resend-email-signup-confirmation

Describe the problem

Problem: The current documentation does not clearly address how site operators can resend confirmation emails to users who have not verified their email addresses post-registration. This situation commonly results in a user lockout where the user cannot log in without verifying their email, and the site operator does not have access to the user's email to resend the confirmation link if it was not saved externally at signup.

Why is it confusing?

The documentation lacks a clear explanation or workaround for resending emails to users who can’t log in because their accounts remain unverified.
There is no mention of how to handle or access user emails for resending confirmation emails without manual database queries or external email storage solutions.
Describe the improvement

Needed Improvement:

Update Documentation: Include a section that explains how to handle unverified users who haven't confirmed their emails. Specifically, provide guidance on how administrators can resend confirmation emails or allow users to trigger a resend of the confirmation email themselves.
Code Example Addition:

const { data, error } = await supabase.auth.resend({
  type: 'signup',
  email: 'user@example.com',  // Dynamically use the user's email
  options: {
    emailRedirectTo: 'https://example.com/welcome'
  }
});

User Experience Issue:
Without the ability to resend verification emails easily, users who miss their initial verification email are likely to abandon the registration process due to inability to log in. This can significantly impact user retention and satisfaction.

[encima]

Thanks for opening!

The code you provided does resend the signup confirmation and is designed to be triggered by the user on the client side where they would provide their email. Is that what you would like to see in the documentation or did I misunderstand?

[SergejSi]

Okay, I will handle it this way. I really miss the ability for users to log in with an unconfirmed email and then be able to confirm it. Additionally, if they do not receive the confirmation link, they should be able to click on a button to have the confirmation link resent.

But for now, I will proceed with the input email form field. Thanks for your response.

[encima]

There is the option of using the new Anonymous Auth for similar behaviour.
Alternatively, you can remove the need for email confirmation and implement the logic on your side to create the behaviour you describe.