Hey, in the below example we block a user from signup if it's not pre-approved by the admin let's say. How do we do the same for third-party login via google? Do we even have access to

email

field before we create the user in the super tokens database and initiate a new session? TIA! https://supertokens.com/docs/thirdpartyemailpassword/advanced-customizations/apis-override/custom-response/general-error

hey @butterballaf - if you override the signInUp recipe function, you do have access to the email before the user is created in supertokens. Have a look at this page: https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/disable-sign-up/thirdparty-changes

Thanks, yeah this works! 🫡