# How to prevent users to see a same data? **URL:** \ **Category:** Ask for Help\ **Created:** [November 22, 2021, 9:09am UTC](https://community.glideapps.com/t/how-to-prevent-users-to-see-a-same-data/34897 "2021-11-22T09:09:41Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [November 22, 2021, 9:39am UTC](https://community.glideapps.com/t/how-to-prevent-users-to-see-a-same-data/34897/3 "2021-11-22T09:39:23Z")
This is a concurrency issue, and it’s a known issue with Glide. Moving to Glide tables will minimise the effect, but it won’t solve the problem completely. To fully solve it, you essentially need to introduce a 3rd party to act as a proxy/arbitrator. I described an approach below, using Integromat: > [@Row Numbers](https://community.glideapps.com/t/row-numbers/27619/11): > > I do believe that if you had just a single GSheet, then you could solve your problem. I’m not sure what your current user journey looks like, but it would need to be a two step process, with a short delay in between each step. Here is what I’m envisaging: When a user taps a button to claim a collectable, you put them into a “holding pattern” The button that they tap sends a webhook to Integromat with two values: the UserID, and the ID (RowID?) of the item they are attempting to claim. Integrom… --- _[View the full topic](https://community.glideapps.com/t/how-to-prevent-users-to-see-a-same-data/34897)._