# Table relations & choice as filter

**URL:** <https://community.glideapps.com/t/table-relations-choice-as-filter/44004>\
**Category:** Ask for Help\
**Created:** [July 6, 2022, 10:29pm UTC](https://community.glideapps.com/t/table-relations-choice-as-filter/44004 "2022-07-06T22:29:30Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [July 7, 2022, 3:53pm UTC](https://community.glideapps.com/t/table-relations-choice-as-filter/44004/6 "2022-07-07T15:53:22Z")

</div>

Now that you brought this up, from a design perspective I read (thought I read/thought I understood) that you should _not_ use the ‘user profile’ table except for ‘user’ info from a security perspective.

But the user profile is the one table that is accessible in actions, visibility and filters so it has become a _very_ wide row with lots of USC/xxx columns with many templates/filters plus relations and is the source for four of my five TABs and many ‘New Screens’,

Is this a reasonable/usual best practice? I especially needed access to data within actions which have a very limited scope.

TIA

---

_[View the full topic](https://community.glideapps.com/t/table-relations-choice-as-filter/44004)._