Back
Why email verification update must be done with a logged in user client?
Althought I found some posts about scope errors, I couldn't find other people asking for this, but I really wanted to know why you cannot update the email verification status without a logged in user.
Would it be that bad to be able to use an admin client? What about users accessing verification link from devices where they are not logged in? Then... Must I force my users to login when they access the verification link?
I found this verification flow a bit complex and unintuitive for the final users π
TL;DR
Developers are questioning why email verification updates must be done with a logged-in user client. They are concerned about the complexity for users accessing verification links without being logged in. Consider allowing use of an admin client or finding a more intuitive verification flow to improve user experience. 