# March 5, 2026 / 🙈 Hide Entity Views with rules, Specify which Entity View to open by default for a user, Validation rules on Create
**URL:** 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
**Category:** Changelog
**Created:** [March 5, 2026, 12:59pm UTC](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 "2026-03-05T12:59:49Z")
**Posts on this page:** 9
**Page:** 2
### Author:  [@Bronn](https://community.fibery.io/u/Bronn)
#### Post date: [March 6, 2026, 12:08pm UTC](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/21 "2026-03-06T12:08:53Z")
> [@mdubakov](#):
>
> Hide Entity Views based on rules
This is huge! Looking forward to simplifying my entity views for users. Thanks team!
> [@mdubakov](#):
>
> Validation rules on Create events
Also useful - a few times I’ve wanted to create a validation rule on creation, so I might use this feature more now.
> [@myg\_ge](#):
>
> I’ll also pray for [“Filters aren’t applied because they have missing ‘𝑥’ dynamic values”](https://community.fibery.io/t/filters-aren-t-applied-because-they-have-missing-dynamic-values/4560) and the new Visibility Rules for buttons, etc.
I’ll second this!
---
### Author:  [@smoran](https://community.fibery.io/u/smoran)
#### Post date: [March 6, 2026, 2:46pm UTC](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/22 "2026-03-06T14:46:19Z")
---
### Author:  [@mdubakov](https://community.fibery.io/u/mdubakov)
#### Post date: [March 9, 2026, 12:51pm UTC](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/23 "2026-03-09T12:51:03Z")
> [@ccollins](#):
>
> This isn’t working for me. The user groups relation isn’t showing as an option in the hide conditions. My user group database is a many-many with users, is that the reason?
We will add it soon
---
### Author:  [@Jonathan1](https://community.fibery.io/u/Jonathan1)
#### Post date: [March 10, 2026, 2:40pm UTC](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/24 "2026-03-10T14:40:45Z")
> [@mdubakov](#):
>
> **Architects** : Now you can still add Views, setup Views and delete Views when Architect mode is off.
Will it be possible to extend this to Spaces and Entities ?
User mode → See only Spaces and Entities I have access
Architect mode → See all Spaces and Entities
---
### Author:  [@B\_Sp](https://community.fibery.io/u/B_Sp)
#### Post date: [March 12, 2026, 6:02am UTC](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/25 "2026-03-12T06:02:33Z")
> [@mdubakov](#):
>
> **Different entity types in one database.** When a database stores multiple types of work (for example Projects and Service Calls), some views may only apply to one type.
Not sure anybody is up for a response here, but I just wanted to sanity check my understanding of this point: In this example are we assuming that the db in question here would have some name of its entities that is the same as the db, so say “work items.” So the db would be named “work items” and consequently so are all the entities in that db. If there are 2 “types” as mentioned here, that would have to be a tag of some sort - so Work Item of type “Project” and work item of type “service call.” And the multi-view feature here allows for a different view depending on the tag - which could be a single-select field.
I definitely have examples of this in my instance, one would be “story” as a db for dev work, and two types we have used are “user” and “technical,” so in this case I could use a different view depending on the type of story…
One reason I wanted to check here is once upon a time databases were actually called “types” so this terminology had me thinking too.
Thanks!
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [March 12, 2026, 6:33am UTC](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/26 "2026-03-12T06:33:38Z")
> [@B\_Sp](#):
>
> I just wanted to sanity check my understanding of this point
Your understanding is correct 🙂
---
### Author:  [@B\_Sp](https://community.fibery.io/u/B_Sp)
#### Post date: [March 12, 2026, 7:04am UTC](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/27 "2026-03-12T07:04:08Z")
Thank you appreciate you getting back on this!
---
### Author:  [@mdubakov](https://community.fibery.io/u/mdubakov)
#### Post date: [March 12, 2026, 1:33pm UTC](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/28 "2026-03-12T13:33:50Z")
> [@ccollins](#):
>
> This isn’t working for me. The user groups relation isn’t showing as an option in the hide conditions. My user group database is a many-many with users, is that the reason?
Added in latest release
> [@March 12, 2026 / moon\_viewing\_ceremony Better file support in Table View, Block reordering in text editor via keyboard shortcuts, History API](https://community.fibery.io/t/march-12-2026-better-file-support-in-table-view-block-reordering-in-text-editor-history-api/10537):
>
> moon_viewing_ceremony Better file support in Table View Working with files in Table View just got easier. You can now upload files directly in table cells: click +, press Enter, double-click on focused cell, or simply drag and drop a file into a cell. Files can be previewed or downloaded right from the table. We’ve also added new ways to display files, including Compact List, Count, and Gallery views. smiling_face_with_sunglasses Block reordering in the Editor via keyboard shortc…
---
### Author:  [@cannibalflea](https://community.fibery.io/u/cannibalflea)
#### Post date: [August 24, 2026, 9:05pm UTC](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/29 "2026-08-24T21:05:33Z")
I’ve noticed that criteria like “is Empty”, “is Not Empty”, or “Contains” , “greater than/less than, …” are not available in view rules. I am wondering if there is a special reason for this or if that is something that will be coming in future releases.
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 create a feature request:
> [@Provide additional entity view rule operators/criteria](https://community.fibery.io/t/provide-additional-view-rule-criteria/11253):
>
> 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 tho…
[Previous page](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.md?page=1)