yes it is. Checkout this example: https://github.com/supertokens/supertokens-auth-react/tree/master/examples/with-thirdpartyemailpassword-passwordless

Thanks, I actually already have Social + Passwordless set up. What I meant was: I want to have some users only see Social, and some only see Passwordless. I suppose having a separate route would be best, like

/signin

for the regular Social signing, and

/confirm

(or something) for the passwordless signin. So far all the recipes seem to have only a single UI, so maybe it's not possible?

(for some users)

(before they login)

so yea.. you can follow the example above, but just don't show the passwordless login button in the thirdpartyemailpassword login

and i think the example already has both those login methods on different paths anyway

I can see how the UI changes with the existence of the query Param (social when

rid=thirdparty

or rid is undefined, and passwordless when

rid=passwordless

). Is this documented somewhere? Can I rely on this "feature" to remain stable? Also, out of curiosity, are there docs to describe any other query params? Or do I need to dig into the code to figure it out?

There arent any specific docs for query params.

But the other one is the “show” query param which takes a signin / signup value. And shows that form (applicable only to UI in which there is a diff sign in and sign up form)