Hi There,
I’m a complete novice at this so may be asking very basic questions. I’ve created a signup/signin page. My expectation is that when a user signs up their details are populated to the data tables and then authenticated when they sign in. Glide’s AI says the process on Glide doesn’t work like that and works as summerised below:
This is the standard behavior in Glide. Rows are added to the users table when users login for the first time, not during signup.
How the Process Works:
- Signup: Creates the user account in Glide’s authentication system
- First Login: Adds a row to your users table with the user’s email and profile information
The issue I’m facing is that every time I sign in, even with the exact same credentials, a new row is created in the user table, as if it’s treating me like a completely new user. There seems to be no connection between the sign-up and sign-in processes. What I need is for users to sign up once, be recognised and authenticated on sign-in, and have their previously entered details pre-populate when they access certain features so they don’t have to re-enter information they’ve already provided.
I’m not sure if I’m misreading what the AI is saying but I would appreciate some clarity please. Thanks in advance.
There is no difference between the Sign Up and Sign In buttons in Glide. They both function the same. When a user logs into the app for the very first time, a new row should automatically be created in the user table. It should not create a new row for subsequent logins. That is all without creating any sort of screens yourself.
You mentioned creating a screen for your sign up process. Please share more about that and what a user experiences every time they sign into your app. I feel like you may have created something that always adds a row when it shouldn’t.
The normal flow is that a user signs in the for the first time. A row is automatically generated. Then you direct the user to that row to complete their user profile.
2 Likes
The sign-up page requests the user’s details, including creating a password, and then navigates to the next screen where the user must enter their username and password. The username is the email, and the password is whatever they created during signup. However, instead of the signup details populating the tables, only the sign-in details show up, and every time someone signs in, it creates a new row even though that person has already used those details to sign in.
If I’m understanding correctly you’re saying that sign in should come first and then the user needs to be directed to the page that I have as sign up to complete the details. If that’s correct, then where does the user get their sign-in credentials or do they use their Google accounts?
I’m going to stop you right there. Creating your own sign in screen and authentication instead of using Guides built in authentication is not secure in any respect and possibly a violation of Glide’s T&C.
I’m sure your setup has something to do with adding a row instead of updating a row, but the way you are handling authentication means anybody could snoop the data and figure out other user’s passwords, thus is not secure. I do not recommend doing it this way.
Use Glide’s built in authentication if you want any chance of properly securing your user’s data.
4 Likes
OK, it’s my bad I’ll read about it. I was in a hurry to get the app built so, I just assumed it could be done. Thanks for your response. Appreciate it 
1 Like
