How do we handle signups where the user doesn't own the email address?

Need help Database
1

I’m trying to wrap my head around this problem…

How are we supposed to handle signups where the user doesn’t own the email address used during the sign up process?

I see that it allows them to sign up even if they don’t own it. I was hoping that “send an email to confirm the email” would work but Bubble appears to add the user BEFORE they confirm the email address. Shouldn’t this happen afterwards?

Use case: John Hacker signs up using Mike Smith’s email address (mike.smith@gmail.com). An email is sent to confirm the sign up but is never clicked because he doesn’t have access to that inbox.

A year later, Mike Smith tries to signs up using his email address but then gets a “this email address is already in use”

What am I missing here?

Thanks, guys

2

Hi you can sign-up using asking user id and by default creating email id as user id append with @yourdomain.com

This will allow user to login via without email. Only thing remain you can’t confirm user since no actual email is created

1 Like
3

You can schedule a delete thing (user) + save the scheduled id in the current created user.

In the scheduled workflow you can set it to 48h (or more) to verify the address or the user will be deleted.

If the user enters the validation link add one workflow at the end of the validation that cancels the scheduled id of the current user.

That should work for your use case.