Flexible email verification logic

[wadclapp]

Feature request

Is your feature request related to a problem? Please describe.

On authentication settings, if I select

"Enable email confirmations" // true

The user does not get logged in on signUp, I would like the user to be able to upload an avatar on signup but security policies block it because they're not logged in.

"Enable email confirmations" // false

Email is automatically confirmed, email_confirmed_at etc on auth.users is set as confirmed, no email confirmations are sent.

Describe the solution you'd like

Split the option into 2, e.g.
"Enable email confirmations" - allows signin, but email is not confirmed, I as the developer handle this state of unverified users myself in my app
"Require email confirmation for signin" - if not checked, signup logs user in, but email is not confirmed, and if "Enable email confirmations" the email verification email still gets sent out

Also, in postgres an auth.emailVerified() function or something would be nice to check if user is verified :)

Describe alternatives you've considered

Additional context

[hf]

Thank you for this issue. This is something we're going to look into fixing and I've added it in our backlog. We can't promise any timelines yet.

[J0]

Added as potential use case for triggers

[devjume]

Any update on this?

I am looking for following sign up flow but it is not possible at the moment.

1. User signs up
2. User is automatically logged in
3. Sign up confirmation email is sent automatically
4. User confirms the sign up at later time (I take care of reminding user about this in the app)

Of course I can setup some automation to send email from my own email handler but it feels kind wrong. And then I cannot utilize Supabase email templates or verification tokens etc.

I also found following discord message requesting same: 1172861913433129041