How can the user get to the Home screen when logging back into the application and see his previously entered data?

Hello, I have this problem. I have the entire database, including users in Airtable. Can anyone tell me how, after registering, when the user logs back into the app, to get to the Home screen and see his previously entered data?

I pulled the entire database from Airtable into Adalo and it is already fully displayed in the app. Everything works fine. I can’t figure out how to make Adalo remember the registered user, show him the “home” screen when he logs in again and show him the data he entered earlier, which has already been saved in the Airable and is waiting for him again.

Provide more information and screenshots.

We do not know what you have on the home screen, what’s being displayed when a user first logs in, or what the user sees when they log back in.

The entire database is located in Airtable. I need that after the person has registered and logged into the application again, he was shown the data from the Airtable that he entered during registration. But how does Adalo know it’s him?
I can do this if I work with the internal database, then Adalo understands that this is the same user and getting to the “home” screen, the user sees the information that he entered earlier. But Adalo does not understand that this is the same user that Airtable created in the table. A person must be logged in when re-logging in and see the information that was created in the Airtable during his registration.

Can anyone help me here?

You have to use an identifier in your airtable database and link that to your user database in adalo.
Like if you have a user ID # in airtable, add a parameter to your internal users and called “Airtable user id”
Then, whenever you need information displayed, filter by that logged-in user > airtable user id.

Thanks! But how can they be connected? Through a certain service? And I don’t understand how to put such a filter on each of the components. For example (photos, sheets). Maybe you mean a filter for something else?
I tried linking via zapier, but it doesn’t link the data, it just adds it and clones it to another service.

No, through the way I mentioned it. You have to have a unique user identifier in your airtable database and then set that as a parameter on your internal user database.

Then, whenever you have a query for something, you would query it using the logged-in user > airtable user id identifier.

For example, I have a list of users where they are users on my adalo database and a user on my Wordpress website.

There is a “user id” parameter in Wordpress that I have linked to the users in the adalo database. When a user logs into the app in adalo, they are able to view all of their Wordpress account info by filtering the a simple list of users where the logged-in user Wordpress user id is equal to the current Wordpress user id.

I’m starting to understand something. But how exactly do I link the id in the airtable and in the internal adalo database? How exactly should they be linked to each other?
Yes, I can make it so that a unique id is instantly created in the airtable database during registration.
But how can I make it so that an identical id is also created in adalo at the same time?

I understand that when the user logs in to the application a second time, adalo should understand that this id is the same user and show him the information he previously left in the airtable, but I don’t understand how adalo will understand that if the logged in user has the conditional id “12345” in the internal adalo database, then it should show all the user information from the airtable with the same conditional id “12345”. I guess this is solved by a binder, which I don’t understand how to do.

This is the last thing I have to do to make the application ready. Would appreciate if you could try to explain it again.

You don’t “link” them, you add the unique identifier as a database parameter to your user collection.

Whenever you have a query from the airtable db, you use the logged-in user’s unique identifier as a query parameter.

Ok, so it’s like this. A user signs up on your app. You set a unique ID parameter for the user. You then have a custom action that would create the user in the airtable database, ensuring that you use the same unique id parameter in the airtable database that you used in the adalo database.

Then, when you add a list to a screen of the airtable database, you use a query where airtable user unique id is equal to logged-in user unique id.