# What if entity view was treated as a dashboard? **URL:** \ **Category:** Ideas & Features\ **Created:** [February 21, 2025, 10:08pm UTC](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322 "2025-02-21T22:08:35Z")\ **Posts on this page:** 5\ **Page:** 2
**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:** [October 8, 2026, 12:38pm UTC](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322/21 "2026-10-08T12:38:16Z")
Check Custom App as Entity View, it should solve this problem [October 1, 2026 / đŸ”„ Custom Apps as Entity Views, Suggestion mode for rich text](https://community.fibery.io/t/october-1-2026-custom-apps-as-entity-views-suggestion-mode-for-rich-text/11348) ---
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [October 15, 2026, 6:11am UTC](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322/22 "2026-10-15T06:11:13Z")
It doesn’t, but assuming it did Why should I be forced to code a custom solution when the capability of adding views and dashboards underneath entities already exists within smart folders? Is it too much to ask for those be converted into tabs? ---
**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 15, 2026, 7:51am UTC](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322/23 "2026-10-15T07:51:40Z")
> [@AdVhPkgKad](#): > > Why should I be forced to code a custom solution when the capability of adding views and dashboards underneath entities already exists within smart folders? Is it too much to ask for those be converted into tabs? It’s a reasonable request, but we have limited developer resources, and when looking at how to prioritise, we always take into account whether the requested use case has existing solutions/workarounds. In this case, custom entity views do address the basic need, even if they might not be quite an out-of-the-box solution. > [@AdVhPkgKad](#): > > Why should I be forced to code 
 You shouldn’t need to do any actual ‘coding’ 🙂 ---
**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 15, 2026, 7:52am UTC](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322/24 "2026-10-15T07:52:26Z")
> [@AdVhPkgKad](#): > > It doesn’t Can you elaborate - what is it that you can achieve with a dashboard that you can’t achieve with a custom entity view? ---
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [October 15, 2026, 9:19pm UTC](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322/25 "2026-10-15T21:19:15Z")
What, aside that a custom view breaks all conventions? Or that users absolutely hate how every custom module feels completely foreign? That it doesn’t piggyback off existing Fibery functionality to display tables and feeds? Take your pick. When all the feedback I’m getting is that it’s “like there are fifty different apps” and “too confusing to use, so I don’t use it”, then the system has failed. Yes I’m frustrated. I’ve just spent the past two weeks trying to get people actually using the app. My manager is breathing down my neck about it. [Previous page](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322.md?page=1)