# \[DONE\] Individual Layouts for a node, hide fields etc **URL:** \ **Category:** Ideas & Features\ **Tags:** entity-view\ **Created:** [September 18, 2020, 8:51am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995 "2020-09-18T08:51:36Z")\ **Posts on this page:** 7\ **Page:** 6
**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\ **Post date:** [August 7, 2024, 12:04pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/103 "2024-08-07T12:04:01Z")
With so much uncertainty I would down scope to: a. Users can specify a default entity view to show for a db view entry point b. Users can select a entity view and that becomes their preferred entity view (but a. overrides b.) Then just beta test this and observe usage and response before fully committing to the final implementation. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 7, 2024, 2:45pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/104 "2024-08-07T14:45:15Z")
I tend to agree that per-view setting will be useful. ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [August 7, 2024, 4:12pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/105 "2024-08-07T16:12:57Z")
> [@mdubakov](#): > > > Is that also the idea of entity views? That a user can switch between views so that the page is less overwhelming? > > Sure, any user can switch views from the list. Not all views will be relevant for the user. Since some of the views are never relevant if you look at the context (example: when you never write content about a subject, then the view with content items is never relevant). So I think it will be confusing for users. > [@YvetteLans](#): > > The problem is that we also have pages where all views are relevant; but there are just **too many** of them. Also on these kind of views it’s not that UI friendly to switch between views as shown in the demo video. > [@mdubakov](#): > > Please note that Multiple Entity View features will be in Pro plan only. The following is not based on the price, but purely the difference between ‘basic’ and ‘pro’. It feels odd that such a common problem (having too many information on a page) can be only solved when you have a Pro account 🤷🏻‍♀️ I can understand that if you only want to show views to certain people with certain roles that it’s logic that you need a Pro account. But isn’t it a bit odd that if a user purely wants ‘tabs’ to avoid information overkill that they need the most expensive version to achieve that? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 8, 2024, 12:48pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/107 "2024-08-08T12:48:13Z")
First release of Multiple Entity Views is here > [@August 8, 2024 / octopus Multiple Entity Views, Group notifications by entity, and moooore](https://community.fibery.io/t/august-8-2024-multiple-entity-views-group-notifications-by-entity-and-moooore/6486): > > octopus Multiple Entity Views (Pro plan only) Multiple Entity Views allow users to create and manage multiple layouts for any database entity. For example, you can configure several Entity Views to display Feature entity differently: NOTE: Multiple Entity Views are available in Pro and Enterprise plans only moneybag. What problems it solves? Sometimes database can be large with dozens of even hundreds of fields, and different users in different context might want to work with some su… ---
**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\ **Post date:** [August 8, 2024, 3:05pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/108 "2024-08-08T15:05:00Z")
Kinda have to agree here – I think that multiple views solves so many problems for new users (Fibery _can_ be a bit overwhelming at first), that it’s a bit of a shame to have it only on Pro plans. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 16, 2024, 8:09am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/109 "2024-08-16T08:09:26Z")
Closed on August 16, 2024, 8:09am UTC ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 18, 2025, 2:04pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/110 "2025-09-18T14:04:12Z")
This feature was released today, please check [September 18, 2025 / ⚔️ Specify which Entity View to open based on some field value](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616) [Previous page](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995.md?page=5)