Hi; Can you confirm the email-verification step is done explicitely after the signup promise resolution; in a non blocking way ? That's important to us, as we modified the signup, which now includes an internal db transaction to create a user in our database. This user is not "visible" outside of the transaction before it resolves; and later we might "find" this user before sending the verification email (we also override the email send).

hey @Chimanos yes that is correct. For login methods which do not already verify emails, first the sign up and session creation process is completed, and only after that the user is sent into the email verification flow. For other login methods like sign in with google, passwordless, where the email is already verified during user creation, we first create the user -> mark their email as verified -> create a session.

Alright, thanks 🙂

the user context is per API call