# Row owner column. How to make common rows?

**URL:** <https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689>\
**Category:** Ask for Help\
**Created:** [May 27, 2024, 2:31pm UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689 "2024-05-27T14:31:55Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pavel\_P](https://avatars.discourse-cdn.com/v4/letter/p/ecccb3/32.png) [@Pavel\_P](https://community.glideapps.com/u/Pavel_P)\
**Post date:** [May 27, 2024, 2:31pm UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689/1 "2024-05-27T14:31:55Z")

</div>

Hi, please help me with advice about row owner column.

I have a table with purchases categories.  
 ![Новый рисунок](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/a/0a43828751ad7865d86daeedb11f353c270d80c0.jpeg)

My goal is to make the first three categories (food, education, car) available for all users. And all other categories have to be available only for the users who created them.

Now if I leave the Email column empty - no one can see the row. But if I add email - rows become visible only for the row owner. I don’t know how to solve this problem. Thanks for the advice!

---

<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:** [May 27, 2024, 3:42pm UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689/2 "2024-05-27T15:42:56Z")

</div>

Do you have to use Row Owners in this case? Could you use a filter instead, where the filter would check if the email is empty or if the the email is the signed in user email?

---

<div class="post-metadata">

**Author:** ![Pavel\_P](https://avatars.discourse-cdn.com/v4/letter/p/ecccb3/32.png) [@Pavel\_P](https://community.glideapps.com/u/Pavel_P)\
**Post date:** [May 27, 2024, 4:14pm UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689/3 "2024-05-27T16:14:13Z")

</div>

Thanks for the advice!  
I’m new to Glide, so I apologize if my question is stupid. The fact is that I use categories on many screens and forms of the application. Do I need to set up a filter on each of these screens and forms? Or I can set up a filter in the table?

---

<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:** [May 27, 2024, 5:22pm UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689/4 "2024-05-27T17:22:30Z")

</div>

Yes, you would have to set up the filters anywhere you need them on each screen. You could possiblity pull it off in the table with a Query or an IF column that only returns a value depending on the user, but either way you’d still have to find everywhere that category table is being used and make a change on each screen.

Generally I use Row Owners when the data in that particular table needs to be secure. If data security is not as much of an issue, then I’ll use filters.

You can accomplish what you want with Row Owners, but that would involve also using Roles and assigning the same role to all users, so your row owner column would contain either a role or an email. It’s more work to set up honestly, and not worth it if you can get away with just using filters. Also eats into your Roles if you need them later for something else.

---

<div class="post-metadata">

**Author:** ![Pavel\_P](https://avatars.discourse-cdn.com/v4/letter/p/ecccb3/32.png) [@Pavel\_P](https://community.glideapps.com/u/Pavel_P)\
**Post date:** [May 27, 2024, 8:21pm UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689/5 "2024-05-27T20:21:53Z")

</div>

@Jeff_Hager Thanks for the advice! But I still don’t understand how to do this. Different screens have different source-tables. So how can I filter a screen which have another source-tables (not Categories)?  
For example: I have Purchase screen (collection of purchases). User can add purchases, for each purchase he have to select a category. I want user sees only three general categories (food, education, car) and the categories he created?

---

<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:** [May 27, 2024, 9:30pm UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689/6 "2024-05-27T21:30:45Z")

</div>

> [@Pavel\_P](#):
>
> User can add purchases, for each purchase he have to select a category.

If this is a choice component then you would filter the choice component. It would not matter which table the screen is attached to. You filter the component, not the screen.

---

<div class="post-metadata">

**Author:** ![Pavel\_P](https://avatars.discourse-cdn.com/v4/letter/p/ecccb3/32.png) [@Pavel\_P](https://community.glideapps.com/u/Pavel_P)\
**Post date:** [May 28, 2024, 11:24am UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689/7 "2024-05-28T11:24:21Z")

</div>

@Jeff_Hager Thank you very much! No, thank you VERY, VERY, VERY, much! I wasn’t good enough at Glide to understand your advice right away. But I re-read it 5 times. And then I re-read it 5 more times. And I GET IT!!! It really works! Thanks for the advice and for patience!

---

<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:** [June 4, 2024, 11:25am UTC](https://community.glideapps.com/t/row-owner-column-how-to-make-common-rows/73689/8 "2024-06-04T11:25:15Z")

</div>

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