# Important Fields **URL:** \ **Category:** Ideas & Features\ **Tags:** navigation\ **Created:** [September 30, 2021, 11:16am UTC](https://community.fibery.io/t/important-fields/2564 "2021-09-30T11:16:05Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [September 30, 2021, 11:16am UTC](https://community.fibery.io/t/important-fields/2564/1 "2021-09-30T11:16:05Z")
> [@\[DONE\] Multi-panel context-preserving navigation](https://community.fibery.io/t/done-multi-panel-context-preserving-navigation/2003/3): > > First, it appears that non-Rich Text fields are all at the top of the layout in this view. This is Notion-like and sucks terribly. 😆 We’ll see how it goes on live data — so far it’s a radical experiment. > [@\[DONE\] Multi-panel context-preserving navigation](https://community.fibery.io/t/done-multi-panel-context-preserving-navigation/2003/3): > > I am _hoping_ this is indicating a future function for selecting a subset of Fields to show by default and hiding the rest (i.e. lesser-used), in which case this is probably fine. Correct, we imagine Creators marking some Fields as important which pins them throughout Fibery. This might include the creation screen as well, similar to Linear: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/606de0b2ec90d33ebe07deb405e95fef52c7e608.jpeg) ---
**Author:** ![Jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@Jean](https://community.fibery.io/u/Jean)\ **Post date:** [October 3, 2021, 9:48am UTC](https://community.fibery.io/t/important-fields/2564/2 "2021-10-03T09:48:25Z")
> [@\[DONE\] Multi-panel context-preserving navigation](https://community.fibery.io/t/done-multi-panel-context-preserving-navigation/2003/3): > > First, it appears that non-Rich Text fields are all at the top of the layout in this view. This is Notion-like and sucks terribly. I completely disagree with this. Maybe it depends how everyone uses Fibery, but having the important fields shown on top it’s great, especially when doing 2 panel navigation. Notion, Coda etc uses this and for sure they have enough UX data to confirm it, otherwise they would at least try changing it. 2 panels will work really well when you have relationship and you want to check those items, or links to other entities in the rich text, it’s so much easier to open the entity in another panel and keep the view instead of having to go back each time. ---
**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:** [October 3, 2021, 11:05am UTC](https://community.fibery.io/t/important-fields/2564/3 "2021-10-03T11:05:29Z")
> [@Jean](#): > > having the important fields shown on top it’s great I guess the important fields might be simple fields for some people, and rich-text fields for others 🤷‍♂️ ---
**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:** [October 3, 2021, 5:46pm UTC](https://community.fibery.io/t/important-fields/2564/4 "2021-10-03T17:46:40Z")
> [@Chr1sG](#): > > I guess the important fields might be simple fields for some people, and rich-text fields for others 🤷‍♂️ Precisely! Which is why it should be customizable, as it already now is. And also why I’m confused by the proposed layout which changes the defaults and the way single column layout is handled. That, to me, seems like a separate thing to do, if at all. Is there complaint that the single column defaults are not good? Am I reading too much into the Figma mockup? 😄 ---
**Author:** ![Jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@Jean](https://community.fibery.io/u/Jean)\ **Post date:** [January 5, 2022, 10:00am UTC](https://community.fibery.io/t/important-fields/2564/5 "2022-01-05T10:00:13Z")
Would be nice to be able to move important fields on the main part of the entity view where the rich text fields are located. Even though i love the multi panel feature, for entities that have important information on non-rich text fields, is annoying to click on that little icon on top right to show the non-rich text fields. If we could somehow add important fields on the main part of the entity view, would be awesome. Or maybe a “favorite” field option, with a star button near the field label to indicate that’s important so when the split view is activated to show it on the main part… or even in non-split view, to see the field on the left side ---
**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:** [January 5, 2022, 10:59am UTC](https://community.fibery.io/t/important-fields/2564/6 "2022-01-05T10:59:12Z")
Yes, this will be done soon as well ![Screenshot 2022-01-05 at 12.55.56 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d4c28c8fd2c25b73efcfcebde836976fb3983c41.png) ---
**Author:** ![Jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@Jean](https://community.fibery.io/u/Jean)\ **Post date:** [January 5, 2022, 1:47pm UTC](https://community.fibery.io/t/important-fields/2564/7 "2022-01-05T13:47:24Z")
awesome! love it ---
**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:** [February 18, 2022, 1:50am UTC](https://community.fibery.io/t/important-fields/2564/8 "2022-02-18T01:50:42Z")
This looks really great. Can’t wait to try these and blocks! I had two questions: 1. Has there been any discussion around allowing view templates in the future that users can flip through to see a different layout (possibly different important fields and in different order). I think a few other tools support this (anytype is the first that comes to my mind). 2. Will the important field property by something that can be controlled in the future a bit more dynamically once we have the ability to control fields visibility, filtering, etc based on conditions (there are quite a few requests in that are so I didn’t link to any)? ---
**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:** [February 18, 2022, 10:16pm UTC](https://community.fibery.io/t/important-fields/2564/9 "2022-02-18T22:16:35Z")
> [@cannibalflea](#): > > - Has there been any discussion around allowing view templates in the future that users can flip through to see a different layout (possibly different important fields and in different order). I think a few other tools support this (anytype is the first that comes to my mind). Not quite the same (I described an example of per-role layout visibility), but it implies the same as you are thinking, I believe: > [@\[DONE\] Individual Layouts for a node, hide fields etc](https://community.fibery.io/t/individual-layouts-for-a-node-hide-fields-etc/995/9): > > I’m sure @AndreasHe can clarify best, but here’s what I understood their meaning to be: I have a Type, Client, which has relationships to both Servers (Type) and Contracts (Type). If I open a given Client Entity, I will see lists of both as Related Entites. If there are many such related Entities, these lists could be long. If I am a Developer (Role), I do not care about Contracts, and if I am a Sales Person (Role) I do not care about Servers. So what seems to be requested here is the ability …