# URL Data Breach

**URL:** <https://community.glideapps.com/t/url-data-breach/74912>\
**Category:** Ask for Help\
**Created:** [July 15, 2024, 8:45am UTC](https://community.glideapps.com/t/url-data-breach/74912 "2024-07-15T08:45:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Massimo\_Ridella](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/massimo_ridella/32/62138_2.png) [@Massimo\_Ridella](https://community.glideapps.com/u/Massimo_Ridella)\
**Post date:** [July 15, 2024, 8:45am UTC](https://community.glideapps.com/t/url-data-breach/74912/1 "2024-07-15T08:45:26Z")

</div>

I have a tool in my business to show ‘Team Leaders’ sensitive information regarding thir team members. The data is filtered to show to every ‘Team Leader’ the people who have the name of the team leader as ‘leader’.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/9/69a96eedc517b4ac77c467eb704416ad7032bb2c.png)

A work collegue has recently accessed the App through a URL saved in the browser History and accessed information regarding a person who he should not see. The data and the filters are correct as once my collegue moved to a different screen, he was no longer allowed to go back to the first screen.

To mitigate this i even put visibility conditions on the collections of data shown in the screen. But every time he accesses the app through that URL it’s like he bypasses all filters and conditions. Any idea how to solve this?

---

<div class="post-metadata">

**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:** [July 15, 2024, 9:30am UTC](https://community.glideapps.com/t/url-data-breach/74912/2 "2024-07-15T09:30:45Z")

</div>

Sounds like they are accessing a specific details screen directly.

A quick (insecure) fix would probably be to apply visibility conditions to the components on the details screen.

To fix it properly you should apply Row Owners. You probably want to use Team Names as Roles (configured in User Profiles), and then use the Role names as Row Owners in your data table.

---

<div class="post-metadata">

**Author:** ![Massimo\_Ridella](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/massimo_ridella/32/62138_2.png) [@Massimo\_Ridella](https://community.glideapps.com/u/Massimo_Ridella)\
**Post date:** [July 15, 2024, 10:48am UTC](https://community.glideapps.com/t/url-data-breach/74912/3 "2024-07-15T10:48:24Z")

</div>

Thank you so much Darren! everything works now

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [July 22, 2024, 10:48am UTC](https://community.glideapps.com/t/url-data-breach/74912/4 "2024-07-22T10:48:24Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.