Auth flow
I have an auth flow that I am wondering how I can best model in Ash.
I have tens of thousands of members that I have the info of, most of which will not log into the app. Maybe up to 10 000 real users, some which will be very infrequent. So I would like to use the magic links only not have them manage a password.
I also want people I don’t know the email address of to be able to log in, and fill some info to be reviewed by a human. Some even turn into volunteers but don’t want to become members. So they should be tracked in a different table.
And finally, I have some members who have the same email address as each other and since I don’t want to manage “couple accounts”, they will have to create distinct emails if they want to log in (if they don’t want to log into the app, it’s fine if they share the same email). So if they want to get into the app, they will get an email telling them to contact us to sort it out. It’s the only case where I will deny a login.
1 Reply
Hmm...I'm not really sure TBH. It sounds like a very custom thing. As a first step it may be worth designing the API (I.e the actions) that you want to support to make this all work