Can entity fields be hidden on a per-entity basis?

[Chr1sG]

Related?

Can we create Sub-Types?

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

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 …