I remember it was recommended to use docs as dashboards, but what if the entity view was the dashboard? At the end of the day, each project will need a dashboard to see open tasks, amount of time spent, etc. Each project is already an entity! Why not each entity is a dashboard? We can already add t…

This would be my dream scenario.

[image] RonMakesSystems: Why not each entity is a dashboard? Imagine I add a rich text field to the Project db (called Dashboard) and therein I write stuff, create an embedded (relation) board view of tasks, add an embedded list of assignees, have a burndown report etc. How does what you are…

[image] Chr1sG: embedded (relation) board view of tasks Do you mean in a RTF or as a multi relation in the entity? Edit: as sorry I just reread. The difference is 1. yes, having it the same accross projects, and also the single field as well, all of the above really hahah. Adding a large loo…

This is kind of what I meant: [image] It’s 3 column layout with 3 different embedded views.

I see, makes sense. Yeah the problems with this are like you outlined: Each project will need to have a dashboard set up manually (or a duplicate template that wont be editable globally if I want to make changes after the fact) Cant put fields on the canvas. (there was feature requests for this to…

[image] RonMakesSystems: Each project will need to have a dashboard set up manually (or a duplicate template that wont be editable globally if I want to make changes after the fact) Yep. I assumed this was core to the use case you have in mind. [image] RonMakesSystems: Cant put fields …

Funny I was just looking at what’s going on with TargetProcess yesterday as some of those views were just fantastic, and obviously we have that pedigree here in Fibery! I hadn’t looked that them in maybe a few years and there is still some stuff, like the more sophisticated Kansan boards, that we j…

can I have some examples of an dasboard like this as an Project entity

I saw this coming up in the roadmap: Fibery I fear it’s creating another artifact where there’s no need for one. What if instead of treating it as a new view, we can change the layout an entity view to a dashboard view. Then the layout of the entity is not the old entity view (applying to all enti…

While it sounds nice, it has some conceptual problems. Dashboard View is well known primitive for any user. It demands a leap of deep Fibery understanding to understand how to create a Dashboard without this primitive. Entity View always has context. Indeed it is possible to create a separate data…

What if entity view was treated as a dashboard?

Ideas & Features

danielbmarsh July 12, 2025, 12:03am 17

I agree with this part. Also, I don’t think this should be limited to dashboards. Tables in an entity or other views would be extremely helpful. I get that there are ways to do this with the To-Many fields, but the experience would be greatly improved if a tab of a multi view entity could be dedicated to a view.

Topic		Replies	Views
Views are a little confusing right now	26	236	September 29, 2025
July 10, 2025 / 🪃 Dashboard View (experimental), Fibery AI (Build mode) is out of experimental, Unlimited self-relations on Gantt View Changelog	42	870	December 18, 2025
[DONE] Individual Layouts for a node, hide fields etc Ideas & Features entity-view	104	8965	September 18, 2025
[DONE] Embed Custom Views into Entity View Ideas & Features blocks	18	4574	August 18, 2022
[DONE] Configurable Dashboards Ideas & Features dashboard	18	3663	July 20, 2023

What if entity view was treated as a dashboard?

Related topics