# July 31, 2025 / Context Dashboards and embed widget, some improvements

**URL:** <https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316>\
**Category:** Changelog\
**Created:** [July 31, 2025, 1:10pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316 "2025-07-31T13:10:56Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Post date:** [August 1, 2025, 12:16am UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/15 "2025-08-01T00:16:29Z")

</div>

@mdubakov Piggybacking a bit on your question about use cases — I realize this isn’t exactly what you were asking, but I think it’s part of the same vision.

Alongside dashboards, I believe **entity context-based views** in Fibery deserve a major upgrade. Imagine an Account entity where:

- The **first pinned view** is a dashboard

- The **second** is a field-based details view

- The **third** is a board showing all related onboarding/support tasks

The UI is already 90% of the way there with relation views inside entity fields. But in practice, some views are **central to workflows** — and Smart Folders don’t cut it. They’re not always a solution, especially when users land on an entity from somewhere _other_ than through the navigation menu.

For example, think of how tasks might currently show in a board view inside an Account entity:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0dd30f0d4034d503e7294c3f6a43af2ab5cef737.png)

There are a few areas where the UI is clunky:

- The entity name feels oddly placed

- On 4K monitors, the board only takes up half the screen

- There’s sometimes a double scrollbar (entity + board)

- There’s a strange “Add Field” button below the board

- And importantly: if I want different task views in different contexts (e.g. board on the Task tab, list on the Account tab), it always defaults to just one

If dashboards and views could be **first-class, standalone views inside an entity** , it would make navigating and working across complex data models much more powerful.

I posted a feature idea about this a few weeks ago, but I’m not sure it fully captured the vision. Just wanted to resurface it here for discussion.

> [@Add Views to Entities](https://community.fibery.io/t/add-views-to-entities/8986):
>
> Sometimes I am on an Entity view that has a lot of related data. And that related data should be more prominent to the entity. Example: On an Account, you may want a view dedicated to Contacts, support requests, orders, etc. Instead of this relation being buried on the page, it should be full page and potentially a pinned view to make it quicker to access. Fibery can already expand these views to full screen: So this would be more about taking this and pinning it as a v…

---

_[View the full topic](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316)._