# Relation View Hide Rules **URL:** \ **Category:** Ideas & Features\ **Created:** [May 20, 2026, 5:04pm UTC](https://community.fibery.io/t/relation-view-hide-rules/10886 "2026-05-20T17:04:48Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ccollins](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@ccollins](https://community.fibery.io/u/ccollins)\ **Post date:** [May 20, 2026, 5:04pm UTC](https://community.fibery.io/t/relation-view-hide-rules/10886/1 "2026-05-20T17:04:48Z")
Relation views should have rules similar to entity views. Specifically the ability to hide or default relation views depending on the entity view. This would make the combination between entity views and relation views much stronger. If you default an entity view for different team roles, then you can make it so their relation views only pertain to them. Instead we have way too many relation views which makes views look messy and people get lost more easily. **Alternate Proposal:** just allow the ability to create empty relation view fields that aren’t tied to one of your relationship fields. It feels like you are already 90% of the way there, because a single relation view field can already have view tabs with different databases that aren’t tied to that relationship field at all. Right now, my only options are to live with messy entity views that have way too many relation views, or create empty databases as a way to do imitate the alternate proposal above, but this doesn’t seem like good data hygiene. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [May 21, 2026, 8:59am UTC](https://community.fibery.io/t/relation-view-hide-rules/10886/2 "2026-05-21T08:59:43Z")
> [@ccollins](#): > > **Alternate Proposal:** just allow the ability to create empty relation view fields that aren’t tied to one of your relationship fields. It feels like you are already 90% of the way there, because a single relation view field can already have view tabs with different databases that aren’t tied to that relationship field at all. Yes!! Related: [What if entity view was treated as a dashboard?](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322) > [@How we handle a view with too many related entities](https://community.fibery.io/t/how-we-handle-a-view-with-too-many-related-entities/8949): > > One of the core benefits of Fibery is how flexible and customizable it is. The flipside of that is that things can easily get messy and out of control, which is exactly what happened to us when it comes to the Task database. The Task as we have customized it in Fibery is by far the most used database. That is because almost everything ties to it: the operational side (worklogs, epics, sprints, runways), system modelling (intents, documents, user interface, etc) and more (feedback highlights, re… > [@Add a view of "Collection" entities within another entity that are not related, just for reference](https://community.fibery.io/t/add-a-view-of-collection-entities-within-another-entity-that-are-not-related-just-for-reference/568): > > Hello again! I agree that Fibery is a much simpler tool to configure and set up than both Notion and Coda. One of the great features are the easy-to-set up relations between entities. You guys have great views as well with your “connections” features between many-to-many relations: I was remarking that in Notion, the best way to duplicate this view is with an embedded db. There are a lot of benefits to that view. However, those are not related entities. So I thought if you co…