Hello all. I’m trying to make public sign-in (without the user being in the user’s table - filling out a profile once they sign in) and I can’t make it work.
I have a “legal” users table with email, photo, role, name, etc. Privacy is set to public and “no user profile”. Users and authentication is pointing to my users table.
Whenever I try to sign in, it says “the email address doesn’t have access to this app”. I’m on a Mac using safari and I’ve deleted the cache and cookies to ensure previous attempts did not create a problem.
What are the requirements for “routing” the user to a form? Which form does the system go to by default? Are the requirements for that form? What else could I be missing.
I’ve read posts, watched videos and tried for hours to make this work. All the info I’ve found refers to previous versions that don’t have the same options for sign in. Is there an up-to-date definitive source I can use to learn>
I am stuck after finishing the rest of the app. Thanks for helping me through this.
I will have registered users. But not pre-existing in the user table. That’s what all the tutorials are about. That seems easy. This is someone coming to a website, giving their email to validate, then filling out their profile to ADD to the user table.
Okay, turns out that is a new design style that has only recently been applied. I had not seen it.
Anyway, @Motte - if you have that option selected then users should not even see a sign in screen. Do you have Manual Publishing enabled? If so, you may need to re-publish your App.
If that’s what you want, then you should configure the Privacy setting as per below:
Yes, there has been changes in the glide settings. Due to time zone difference, I am only replying now. But what @Darren_Murphy said is the right way. Let us know if it works for you.
Ok, I think there were two issues. First, it seems you can’t test if the app isn’t published. Second the wording of the public options is really confusing. It isn’t clear what the No Profile, Required Profile and Optional Profile are referring to. Using Optional and Anyone, along with having the app published allowed me to sign in. It is also awkward to test, but if you create a new user in the Users table with only their email address and you select that email address as the current “viewer”…then go to the sign in screen it will pre-populate the email address and you can continue to the login process. Just thought I’d document those details here for others.
One last question - is there no way to direct the logon to a specific screen? Is the only way to guide them there to make ALL of your screens and menu options not visible except the sign-in screen, then reverse that when they’ve populated the user table appropriately? That seems pretty wonky. You have to remember the visibility setting for every menu option and screen you create. There must be a better way.
Thanks for your prompt assistance gents. I can continue with my app because of your help.
If you want to test on the real app, it is the only way. You can also test in the builder.
No profile means there’s no option to sign in at all.
Required profile means you have to sign in before using the app.
Optional profile means you can access the app without signing in, but you can sign in if you want.
If you mean the screen after signing in, it is the first visible screen to the user at that point.
If you construct your tab visibility conditions correctly, that’s the expected behaviour for an onboarding flow if I understand you right. Why do you have to remember the visibility setting for every tab? I don’t expect it to be complicated, usually it’s just “Onboarded” or not.
