# \[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:** 20\ **Page:** 3
**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\ **Post date:** [June 2, 2021, 3:20pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/41 "2021-06-02T15:20:28Z")
I agree that this is something that would be useful and I assume not super complicated. I end up with a lot of calculated fields to use for filtering within views, which are more complicated than the filtering supports. These calculated fields aren’t really ever needed to be shown and end up being a bit overwhelming for new users. There have been a couple other threads with similar topics to reference and “heart” as well. [Some customizations of entity view, hiding unused fields](https://community.fibery.io/t/some-customizations-of-entity-view-hiding-unused-fields/452) [Individual Layouts for a node, hide fields etc](https://community.fibery.io/t/individual-layouts-for-a-node-hide-fields-etc/995) ---
**Author:** ![webinit](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/webinit/32/5548_2.png) [@webinit](https://community.fibery.io/u/webinit)\ **Post date:** [June 9, 2021, 10:22pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/42 "2021-06-09T22:22:19Z")
I wholeheartedly agree. I would love to see this feature request implemented! ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [June 10, 2021, 3:42am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/43 "2021-06-10T03:42:06Z")
Glad you brought this up @Stepan_Galkin! Since this is basically a duplication of the requests @rothnic quoted, could you please be sure to “heart” those as well? There’s no clear way to know if the Fibery team is counting your request alongside those, so it would be great to get your “heart” of support to leave no doubt! …and I can’t help but mention yet again that we have here another example of fragmented requests in this community that an organized voting / request tracking approach would solve, right @Oshyan? ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [June 24, 2021, 1:53pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/44 "2021-06-24T13:53:32Z")
One particularly useful feature that is relatively new in Jira is the ability to pin fields. Jira is highly customizable, and they added this feature which really helps when you get a ton of fields, which can also happen in Fibery, in particular as long as we don’t have [Polymorphic Relations](https://community.fibery.io/t/polymorphic-relations-when-creating-relation-ability-to-have-entire-app-from-which-to-choose-and-not-just-type/425). Some fields are already pinned, such as “Created by” and “Created date”, but to the bottom of the Entity. In some cases actually I’d like those fields at the top! Thanks. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 24, 2021, 3:54pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/45 "2021-06-24T15:54:37Z")
Yes, please. File this with [Customizable Entity Views](https://community.fibery.io/t/customized-entity-views/1546) ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [June 24, 2021, 4:09pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/46 "2021-06-24T16:09:15Z")
Great point Matt, we need a whole group around this subject…I really wish the team would at least think seriously about grouping requests. I know they won’t do votes as has been discussed many a time, but at least grouping would help organize this board. There is only so much relying on simply searching around in Discourse will do… I might draw the loose analogy of using Gmail with no folders, and having to rely on search only to find stuff… ---
**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:** [June 24, 2021, 5:08pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/47 "2021-06-24T17:08:56Z")
We have this in mind as Important fields. Overall, we are discussing **major** Entity View re-work, that includes new 2-panel navigation, blocks, primary/secondary info sections, etc. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [June 24, 2021, 10:35pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/48 "2021-06-24T22:35:27Z")
Ok that sounds like some exciting improvements indeed Michael. Wishing you guys big success in implementing them soon, my team could really use them! ---
**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 13, 2022, 9:12am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/49 "2022-08-13T09:12:57Z")
3 posts were merged into an existing topic: [Tab Views in Entity Pages](https://community.fibery.io/t/tab-views-in-entity-pages/2931/3) ---
**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:** [November 5, 2018, 7:43pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/52 "2018-11-05T19:43:55Z")
Yes, this is planned till public beta release. ---
**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:** [January 12, 2022, 5:35pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/53 "2022-01-12T17:35:55Z")
Bumping this for additional consideration since I see its on the “NEXT: Consider for near future (1-2 months)” in the current version of the roadmap. Specifically, I would love to see something like Coda’s “Customize view” as shown in the [Fibery vs. Coda. The Power of Workarounds](https://fibery.io/blog/fibery-vs-coda-the-power-of-workarounds/) post. ![asset-5](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a187ea6af70d868b6fec51bb42dddaa7679f76f7.gif) ---
**Author:** ![Jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@Jean](https://community.fibery.io/u/Jean)\ **Post date:** [January 13, 2022, 2:43am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/54 "2022-01-13T02:43:10Z")
yeah, i’m excited about this ---
**Author:** ![AndreasHe](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@AndreasHe](https://community.fibery.io/u/AndreasHe)\ **Post date:** [May 19, 2022, 9:43pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/55 "2022-05-19T21:43:44Z")
I want to bump this now. Still missing this feature. Showing so many fields can lead to confusion, especially when using some just for technical reasongs (calculation). In Notion they implemented a simple show/hide function, which is better than nothing. IMHO a per view settings would be great. ---
**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:** [May 20, 2022, 11:57am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/56 "2022-05-20T11:57:16Z")
This is in nearest future scope, right after [Pin Fields on Entity View](https://the.fibery.io/@public/Public_Roadmap/Roadmap_Item/Pin-Fields-on-Entity-View-25) ---
**Author:** ![AndreasHe](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@AndreasHe](https://community.fibery.io/u/AndreasHe)\ **Post date:** [May 20, 2022, 5:58pm UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/57 "2022-05-20T17:58:17Z")
Yeah! Great! I open a beer to celebrate this info 🎉😁 ---
**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:** [July 21, 2022, 11:58am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/58 "2022-07-21T11:58:47Z")
It is possible to Hide fields on Entity View now > [@CHANGELOG: July 21, 2022 / Hide fields in entity view, GraphQL API, Slack Actions](https://community.fibery.io/t/changelog-july-21-2022-hide-fields-in-entity-view-graphql-api-slack-actions/3090): > > Overview Here is the video that demonstrates all new features. see_no_evil Hide Fields from Entity View Now you can hide Fields from Entity View. It can be useful to archive some fields and preserve the data, or to remove some technical fields that you need for formulas and automations, but don’t really use. There are two ways to do it (if you an Admin or Creator): Click … near any field and select Hide option. Click Fields icon on the top right and Hide/Show some fields. [00… ---
**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\ **Post date:** [July 22, 2022, 8:08am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/59 "2022-07-22T08:08:07Z")
I had commented this in the wrong thread, I add my idea/suggestion here as it’s more fitting: I give an example: Let’s assume I have a dataset of documents. There are different categories of documents, indicated by a single-select field “Document type”. Depending on the document type, I might want to see different fields, and even different rearrangements of the fields. I continue with a suggestion: Let’s assume you could rearrange and resize fields within entity view. You could have any view you want, always just for this entity. However, if you could also save the “entity view” now, give the “entity view” a name, you could: - Simply select the desired, pre configured, entity view from the list of saved entity views (within an entity) - Automate entity views via automations by desired criteria. E.g.: ```auto If entity field “document type” updated, then entity view (for step 1 document) = A, if “document type” = X = B, if “document type” = Y else, do nothing ``` Something along these lines? Hope it’s understandable. Not sure if this has been suggested like this before. ---
**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\ **Post date:** [September 9, 2022, 10:27am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/60 "2022-09-09T10:27:53Z")
It’s possible to create Custom Relation Lists now 💖 > [@CHANGELOG: September 8, 2022 / Relation Lists, reorder Databases in Space settings](https://community.fibery.io/t/changelog-september-8-2022-relation-lists-reorder-databases-in-space-settings/3262): > > Relation Lists This feature has been experimental for a while ([https://community.fibery.io/t/changelog-august-18-2022-experimental-relation-views-and-buttons-on-entity-view-promo-codes/3184/2](https://community.fibery.io/t/changelog-august-18-2022-experimental-relation-views-and-buttons-on-entity-view-promo-codes/3184/2)), and now it’s enabled for everyone by default. [image] When you open an Entity, to-many relations are now visualized as proper Views with levels, units, filters, sorting, and color-coding. Our goal is to make Entity View a better dashboard for DBs like Project or Epic. So far it’s only a single List Vie… (slowly improving…) ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 16, 2022, 1:15am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/61 "2022-09-16T01:15:11Z")
Just wanted to note that I saw this is next, and it’s a bit exciting: > **[Collapse and expand Fields on the left on Entity View](https://the.fibery.io/@public/Public_Roadmap/Roadmap_Item/Collapse-and-expand-Fields-on-the-left-on-Entity-View-109)** > > Tailored workspace for your company. Connected databases, customizable views, powerful reports, automations, integrations, docs & whiteboards. However also wanted to note that my visceral reaction was “Dang, just collapse? I wish we had full, unique, savable layouts per-DB”. I know, it surprised me too, but that’s what I wanted. 😄 Which is to say, individually-remembered collapse states per-DB layout is great, and it may be that for many roles a single state will represent their needs fairly consistently. But for me as a “jack of all trades”, interacting with a lot of different data in different ways at different times, I’d love to see more fully articulated and separately displayable (even linkable?) view setups/templates. I think this would also apply well to e.g. publishing of Entities, where the configuration if the view wouldn’t necessarily be desirable as an end-user feature, and yet you want to be able to show particular view configurations to the general public, vs. different ones internally, etc. All that said I’m still excited collapsible “left pane” fields are coming! ---
**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:** [September 16, 2022, 5:42am UTC](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995/62 "2022-09-16T05:42:36Z")
> [@Oshyan](#): > > I wish we had full, unique, savable layouts per-DB” Do you mean that each user would have their own personal set of multiple layout choices, per db? Or just that a db would have a set of views which all users choose from? [Previous page](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995.md?page=2) [Next page](https://community.fibery.io/t/done-individual-layouts-for-a-node-hide-fields-etc/995.md?page=4)