# Row Owners vs. Filters

**URL:** <https://community.glideapps.com/t/row-owners-vs-filters/37125>\
**Category:** Ask for Help\
**Created:** [January 13, 2022, 5:58pm UTC](https://community.glideapps.com/t/row-owners-vs-filters/37125 "2022-01-13T17:58:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [January 13, 2022, 7:48pm UTC](https://community.glideapps.com/t/row-owners-vs-filters/37125/2 "2022-01-13T19:48:51Z")

</div>

As far as filters are concerned, everything is done client side. About the only client/server interaction is to synchronize data changes between glide’s copy of the database and the client’s copy of the database.

Row Owners are a security feature which restricts which data is sent to the client in the first place.

Row owners need to be basic columns. You can’t use computed columns because computed columns are computed only on the user’s device after the data has been synchronized to them. At that point, data security is a moot point if you wanted to apply row owners to computed columns. The only loophole is to create an array via a google sheet, because a sheet array is not computed data. It’s still basic static data, so you can apply row owners to an array column generated from sequentially numbered Google sheet columns.

---

_[View the full topic](https://community.glideapps.com/t/row-owners-vs-filters/37125)._
