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…

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…

I see, and understand it makes things a bit more complex, but I don’t completely agree. Especially with the upcoming shift from Documents as views to a default documents database, you could make the same argument that documents are a primitive that people understand and should therefore be their ow…

One point worth noting is that entity view currently allow you to arrange (hide/show/reorder) fields, including relation fields. To-many relation fields can be displayed as various different views (list, board, table, etc.) but there is only one visible view per relation (you can have tabs, but only…

[image] Chr1sG: As far as I understand it, dashboard view will allow for any number of embedded views, each of which is context filtered to the specific entity. Exactly! It’s related to this: Add a view of "Collection" entities within another entity that are not related, just for reference , a…

[image] RonMakesSystems: I’m proposing a toggle for “Same dashboard for all [database name]s” or “Unique dashboard per [database name]” This is the same concept as context views in smart folders - they can be mirrored (same for all entities) or they can be unique. A ‘dashboard view’ in a smar…

What if entity view was treated as a dashboard?

Ideas & Features

mdubakov October 8, 2026, 12:38pm 21

Check Custom App as Entity View, it should solve this problem October 1, 2026 / 🔥 Custom Apps as Entity Views, Suggestion mode for rich text

Topic		Replies	Views
Views are a little confusing right now Misc	26	321	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	1038	December 18, 2025
[DONE] Individual Layouts for a node, hide fields etc Ideas & Features entity-view	104	9376	September 18, 2025
[DONE] Embed Custom Views into Entity View Ideas & Features blocks	18	4668	August 18, 2022
[DONE] Configurable Dashboards Ideas & Features dashboard	18	3798	July 20, 2023

What if entity view was treated as a dashboard?

Related topics