When a user enters information on the welcome page, we use that data to show them personalized content.
The information from the welcome screen is saved to the Users table and retrieved from the same table on the personalized content screen. To ensure each user sees only their own content, I have set a filter on the personalized screen: Email is Users > Email. If I remove the filter, the information displayed is not personalized, so I believe the filter is working correctly.
This works perfectly when testing inside the Glide builder or app preview. However, when I test the app externally (via the share link), I run into an issue: after a new user signs up and completes the welcome flow, no content shows up on the personalized content screen, even though the data is present in the table.
I have also tried adding an intermediate screen and even introducing a delay before showing the content screen, but none of that helped.
To summarize:
The issue only occurs when testing the app via the share link
User data is correctly saved in the Users table
The screen is filtered to show content only for the signed-in user
No content appears when testing outside the builder
Removing the filter displays non-personalized content
Has anyone else run into this? Could it be related to filter logic, visibility settings, or a timing issue with data syncing?
Happy to share more details if helpful thanks in advance for your help!
Are you creating a second user row for the same user when they complete the welcome flow, or are you updating the original row that is created automatically when they sign in the first time?
When I use Glide’s built-in authentication, it creates two rows—one with just the email, and another with all the info (including the email).
However, in this case, I am not using Glide’s authentication or any profile creation. So only one row is created when the user completes the welcome flow.
This is because your flow is set up to add a row. You don’t need to add a row because glide adds one for you when the user signs in. Your flow should be updating the existing row instead of adding a new one.
If you are not using Glide’s built in authentication, then it has no way of knowing what data belongs to the user. Plus, you prevent yourself from providing proper data security.
Got it, thanks Jeff, that makes sense. I will switch to using Glide’s authentication.
Quick question: how do I set up the flow to update the existing row instead of adding a new one? Should that be done as an Action when submitting the welcome page, or through a new workflow?
Under Action > Data, I see options to add or delete rows, but not to update.
Here’s my current setup:
The welcome page has text entry fields and choice components that write directly to the respective columns in the Users table (set via the right panel).
On Welcome page form submission, the action is set to Go To Tab → personalized content screen.
On the personalized content screen, I have a filter: Email is Users > Email.
Is there something I need to adjust to ensure the existing row is being updated properly when using Glide auth?
I assume you are using a form or a form container for the welcome screen? I would guess a form container based on your description. Forms will always add a new row when submitted.
Instead, you have a couple of options. First of all, I would make sure the tab screen is linked to the user table and filtered to the signed in user row. From there, you could add a button that opens a separate edit screen, but I think the better option is to place entry components directly on the tab detail screen. Essentially avoid using a form or form container and directly update the row in real time. Since the screen would be filtered, it would update the user’s row.
Just wanted to say a big thank you! I added Glide authentication, rebuilt the welcome screen without the form container, added the email filter, and it worked perfectly.
Your guidance made all the difference. Really appreciate the clear explanation and the quick help!