# Entity view rules are extremely limited **URL:** https://community.fibery.io/t/entity-view-rules-are-extremely-limited/9958 **Category:** Ideas & Features **Tags:** automations **Created:** [November 5, 2025, 8:53pm UTC](https://community.fibery.io/t/entity-view-rules-are-extremely-limited/9958 "2025-11-05T20:53:12Z") **Posts on this page:** 1 **Showing post:** 15
### Author: ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea) #### Post date: [September 5, 2026, 2:01am UTC](https://community.fibery.io/t/entity-view-rules-are-extremely-limited/9958/15 "2026-09-05T02:01:04Z")
> [@March 5, 2026 / see\_no\_evil\_monkey Hide Entity Views with rules, Specify which Entity View to open by default for a user, Validation rules on Create](https://community.fibery.io/t/march-5-2026-hide-entity-views-with-rules-specify-which-entity-view-to-open-by-default-for-a-user-validation-rules-on-create/10491/1): > > 🙈 Hide Entity Views based on rules > 🙊 Specify which Entity View to open by default for a user The view rules are great features and can be super useful in designing more dynamic workflows. However, the filter operators for the rules are limited to a few operators (“is”, “is not”, “contains (any)”, and “does not contain (any)”). It would be really helpful if we had access to all of fibery’s array of filter operators that are available in other areas of the application, in particular things like “is Empty”, “is Not Empty”, or “Contains” , “greater than/less than, …” . I think some of those criteria, e.g. “is Empty” can be helpful to show/hide views that might be needed at initial creation and not needed at other stages of the entity workflow. I am not sure if there is a special reason for this or if that is something that will be coming in future releases. --- _[View the full topic](https://community.fibery.io/t/entity-view-rules-are-extremely-limited/9958)._