# \[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:** 92

<div class="post-metadata">

**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:** [August 5, 2024, 5:59pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/92 "2024-08-05T17:59:15Z")

</div>

@mdubakov This is really exciting news and will make things a lot easier for teams with users who have different requirements.

I think I saw somewhere that one of the next steps might be to use state or other fields to decide which view to show. That would make this even more useful. However, while this makes things nicer for multi-user workflows, it still doesn’t address situations where depending on the current users choices, the creator wants to display different fields, unless the user refreshes the screen so they can be sent to another view. That is why, I wanted to again pitch the possibility to control some fields (or group of fields) using based on conditions:

> [@Setting field/UI properties based on conditions](https://community.fibery.io/t/setting-field-ui-properties-based-on-conditions/5226):
>
> With the excitement and discussions around [[IN DEV] Entity-level permissions](https://community.fibery.io/t/in-dev-entity-level-permissions/2163) I have been thinking about field level permissions. I know that the Fibery team has said that field level permissions are not on the roadmap and unlikely in the near term (see below from recent posts as well as [Field-level permissions](https://community.fibery.io/t/field-level-permissions/2799) request): There has also been some discussion that maybe view permissions and multi entity views might make this not as a big deal: However, I was thinking that there might be another …

---

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