# \[DONE\] Individual Layouts for a node, hide fields etc

**URL:** <https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995>\
**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:** 1\
**Showing post:** 67

<div class="post-metadata">

**Author:** ![ccollins](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@ccollins](https://community.fibery.io/u/ccollins)\
**Post date:** [October 25, 2022, 7:03pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/67 "2022-10-25T19:03:33Z")

</div>

> [@\[DONE\] Tab Views in Entity Pages](https://community.fibery.io/t/tab-views-in-entity-pages/2931):
>
> Apologies if this has already been suggested. I see several customizable entity items on the roadmap (pin views, relation views, hide fields), but I wanted to share the ideal upgrade for my use case. Tabs! Similar to tabs on a web browser or sheets on an excel workbook. I would love to be able to click on an entity and then organize the fields into tabs that makes sense, rather than everything being on one page. Especially for entities like a project, that have a lot of relationships. (Example…

> > I talked about “Views per Entity” on this ideas page. But now that it is being discussed here, it may be best to close it and transfer those votes?

**My use case** : I manage commercial construction projects - My project entities are connected to the following categories:

- _Project Overview_  
(general project info, percentage completion, upcoming summaries, critical tasks, potential cost exposure, inspection tracking)
- _Schedule Progress_  
(tasks, procurement, milestones, MOP approvals, meeting minutes)
- _Trade Management_  
(buyout tracking, cost logs, closeout tracking)
- _Lessons Learned / QAQC_  
(a place to capture new and review automatic connections based on project data)

In my opinion, most entity pages do not need tabs, but the ones that do need it, _really need it_. For example, our task entities don’t need it, but our project entities really do. In my use case above, four tabs is a lot easier to manage than ~20-30 blocks on a single page. Company pages is another example that I would definitely use ‘views per entity’ for.  
With the to-many relations block update, we are using entity pages a lot more than we used to, but with so many to-many relation blocks on one page it is very easy to get lost and waste time looking around.

For user complexity - the drop down view selector is great for to-many relations blocks, but in my opinion drop downs would not be ideal for ‘views per entity’. Big tab buttons that scrolled with the frozen header at the top would make it more intuitive

---

_[View the full topic](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995)._