# Unique data per user **URL:** https://community.glideapps.com/t/unique-data-per-user/6525 **Category:** Ask for Help **Created:** [April 6, 2020, 8:22pm UTC](https://community.glideapps.com/t/unique-data-per-user/6525 "2020-04-06T20:22:29Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager) #### Post date: [April 6, 2020, 9:02pm UTC](https://community.glideapps.com/t/unique-data-per-user/6525/3 "2020-04-06T21:02:58Z")
In addition to @gvalero’s sample app, here’s some different methods to establish unique user records. > [@Hide Elements When User Not Signed In](https://community.glideapps.com/t/hide-elements-when-user-not-signed-in/4723/27): > > You are comparing a column value to signed in user, so it’s looking for a match in that column. Otherwise with your original thinking, there would be no point to compare to a specific column. It would need to check if the user is signed in or not (there is no such check). As for benefits, that depends on your use case. Bringing in emails from App:Logins eliminates a step for the user by automatically creating user specific rows, but you run a risk of emails shuffling around if you use the Un… --- _[View the full topic](https://community.glideapps.com/t/unique-data-per-user/6525)._