# Can entity fields be hidden on a per-entity basis? **URL:** \ **Category:** Get Help\ **Created:** [July 12, 2021, 9:20pm UTC](https://community.fibery.io/t/can-entity-fields-be-hidden-on-a-per-entity-basis/1785 "2021-07-12T21:20:14Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [July 12, 2021, 10:50pm UTC](https://community.fibery.io/t/can-entity-fields-be-hidden-on-a-per-entity-basis/1785/2 "2021-07-12T22:50:11Z")
Related? > [@Can we create Sub-Types?](https://community.fibery.io/t/can-we-create-sub-types/1748): > > I’m wondering if there is a way to do something like this: Create a type, such as “task”, then create a child type of task, say “task for project2” that has all the properties of its parent type, plus any additional fields that I might want to use in that particular instance of the task type. A related question: Is there a way to create field templates that capture your chosen edits to a field’s properties? > [@Polymorphic relations. When creating relation, ability to have many Types from which to choose, and not just one Type](https://community.fibery.io/t/polymorphic-relations-when-creating-relation-ability-to-have-entire-app-from-which-to-choose-and-not-just-type/425/15): > > Just for what it’s worth, there is a program I previously used for doing the stuff I’m now doing in fibery, and it used the concept of subtypes to achieve the result that @Oshyan is talking about That is to say, enabling/disabling field visibility. You could choose for each subtype which type fields were to be visible/accessible. When an entity was created, you had to choose a subtype. It was actually possible to change subtype subsequently, and a minor issue I discovered by experimenting was … --- _[View the full topic](https://community.fibery.io/t/can-entity-fields-be-hidden-on-a-per-entity-basis/1785)._