# July 31, 2025 / Context Dashboards and embed widget, some improvements **URL:** \ **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:** 20\ **Page:** 1
**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:** [July 31, 2025, 1:10pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/1 "2025-07-31T13:10:56Z")
Summertime. So just few quality of live improvements here and there. 🌮 ## Dashboard View is fully ready [Dashboard View](https://the.fibery.io/@public/User_Guide/Guide/Dashboard-View-421) is no longer experimental, so you can safely use (and enjoy) it. Context Dashboards are there, plus you can embed external links as widgets. ### Context Dashboard View Now you can create context Dashboard Views inside [Smart Folders](https://the.fibery.io/@public/User_Guide/Guide/Smart-Folders-26). All Views inside Dashboard will be automatically filtered by the parent entity. For example, in this scenario single Dashboard shows Features and Insights views and reports for the selected Initiative. ![2025-07-31 09.48.37](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8ccbedaac8e0de21671e1e2312bd0210b651bc4d.gif) ### Embed widget for Dashboard Now you can add embeds as Widgets on Dashboard Views. For example, you can add a link to educational video, some website, Figma prototype, etc. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4775fee46e0af98352a830f22df6ff5a548fe0a4.jpeg) ## Enhanced navigation options for Whiteboard We’ve added two new user preference settings to make navigating the Whiteboard faster and more intuitive — just like in your favorite design and mapping tools (e.g., Miro, Figma, Blender or Google Maps). đŸ–± **Scroll wheel zoom** Zoom in and out using your mouse wheel, no Cmd/Ctrl key required 👌 đŸ–± **Right-click to pan** Hold the right mouse button to drag and pan across the Whiteboard. ⚙ You’ll find both options in your Whiteboard action menu. These preferences are set per user and apply to all whiteboards in your workspace. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/ffbf115f6230d31935ffb0bf5f3f56a9c3be48fb.jpeg) ## Simpler auth in import and sync The first step to connect your external tool to Fibery used to be quite nerdy. It featured words like `OAuth` and legacy auth methods. We’ve revamped it to be more welcoming: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/abbe1a9f2da6ccd3ddf472b2f2dac2f44c7ae8cd.png) Our data shows that people strongly prefer OAuth whenever it’s available, so we’ve deprecated token-based auth for all connectors where OAuth is an option. This only applies to new connections, the existing ones will continue to work. ## 🩋 Improvements - **Linear integration:** Blocking Projects are now synced, but an admin should enable “Use relation as dependency” for “Blocking” relation in Project database ## đŸ’© Deteriorations - **Sync data from Slack** : Slack is [changing API rate limits to ridiculously low](https://api.slack.com/changelog/2025-05-terms-rate-limit-update-and-faq). It means our Slack-to-Fibery sync can no longer work. We removed Slack Integration from templates and integration sources. Existing integrations may stop work after _September 2_. Not sure what we can do here so far, but this practice is shitty as fuck
 We hope they will reconsider, but the chances are small. ## 🩐 Fixed Bugs - **Navigation** : An error while attempting to open the collapsed panel - **Timeline View** : - Highlighted area for the last lane is cut for some reason - Backlog layout is broken - **Gantt View** : - Upgrade to Standard instead of Pro button is shown on dummy page when open collaborative Gantt on the workspace with non-Pro subscription - Title from secondary date card overlap with title on primary card - Scroll to edge buttons don’t scroll enough - **Google Calendar Integration** : unexpected entity syncs because of perceived attendees change - **AI Agents** : AI can’t apply filter by rich-text field - **Home Page** : It’s possible to embed mirrored view to home page - **Dashboard View** : - Wrong dashboard layout for narrow screens / in a half-panel - Blinking Fields list if it is opened after ‘
’ menu P.S. We are looking for [Customer Education Manager](https://fibery.io/blog/we-are-hiring/customer-education-manager/). It is our 4th attempt to find a good fit for this position. P.P.S. A safe way to procrastinate your work this Friday: [watch our July updates webinar and see what’s new in Fibery](https://app.livestorm.co/fibery/monthly-product-updates). We’ll cover Dashboard View, creating views with AI, Home Page updates, and more. August 1st, 2 PM CET. Hope to see you there! 😉 ---
**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:** [July 31, 2025, 1:11pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/2 "2025-07-31T13:11:03Z")
---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [July 31, 2025, 1:33pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/3 "2025-07-31T13:33:00Z")
Dashboards looks awesome, thank you! đŸ„ł Although, it appears not well integrated yet as view? The dashboard still appears fully dependent on the left sidebar (and smart folders). Me and other users prevent using the sidebar (focused UI principle). **Dashboards cannot be embedded in rich text fields?** ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d088f5e5559e549845ed0ec70f9e0e0a702d2a5e.png) **And cannot be chosen as Field View?** ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2942d9e00601edc2f58d02b6dfb738177f35be51.png) ---
**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:** [July 31, 2025, 1:35pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/4 "2025-07-31T13:35:24Z")
Any use cases for these things? ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [July 31, 2025, 2:07pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/5 "2025-07-31T14:07:08Z")
USE CASES: 1. **Team Overview Page** **Who:** Team leads, managers, staff **Frequency:** Used daily **Need:** View tasks (Board), deadlines (Timeline), and metrics (Chart) together. **Sidebar issue:** Navigating via sidebar breaks focus—most users avoid it. **Why Dashboard:** Enables a full team cockpit directly in the entity view. * * * 1. **Project Snapshot** **Who:** PMs, product owners, collaborators **Frequency:** Multiple times per week **Need:** Show timeline, task list, and progress chart inside the project entity. **Sidebar issue:** Separate Dashboard access via sidebar is disruptive. **Why Dashboard:** Provides complete project context inside the entity—without navigation overhead. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e99ed930ee0ae5cd3825c8daac7fe6071e36fc89.png) ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [July 31, 2025, 3:02pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/6 "2025-07-31T15:02:00Z")
I really want dashboards to be able to be used INSIDE of an entity because we’re dying for more flexibility on how fields/information on an entity is laid out. The ideal option (that I know isn’t likely to happen anytime soon) is if the entire entity view layout was able to be essentially a dashboard, where we could move fields around as needed. A common use case for this that I know has been requested many times is to be able to have 2 fields aligned next to each other horizontally to fill the crazy amounts of negative space in an entity and reduce the need for scrolling, instead of being forced to have fields vertically stacked like we have now. An alternative might be to allow a dashboard to be a type of field, just like rich text is a type of field, so we can add dashboards to an entity without the (I assume) complexity that comes with making a dashboard context view on a collections field. If this “dashboard field” could be contextually self-referencing so it could easily display any _other_ field that is on the entity, then you’ve essentially unlocked a way to do flexible layouts. Here’s my quick mockup of the later idea: ![dashboard_field](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b2192b730c155561809ef516fc42d59d4e372aea.jpeg) ---
**Author:** ![jandrabek](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jandrabek/32/10414_2.png) [@jandrabek](https://community.fibery.io/u/jandrabek)\ **Post date:** [July 31, 2025, 4:35pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/7 "2025-07-31T16:35:48Z")
I think that since grid is well tested now the solution would be to use grid for entities design. ---
**Author:** ![webinit](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/webinit/32/5548_2.png) [@webinit](https://community.fibery.io/u/webinit)\ **Post date:** [July 31, 2025, 6:12pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/8 "2025-07-31T18:12:11Z")
Why can’t you just add the dashboard style content to a rich text field or to several rich text fields? You can create columns, embed any number of views you’d like, organize it in any format. Doesn’t this get you a large way toward what you’re wanting? ---
**Author:** ![webinit](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/webinit/32/5548_2.png) [@webinit](https://community.fibery.io/u/webinit)\ **Post date:** [July 31, 2025, 6:14pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/9 "2025-07-31T18:14:43Z")
Having finished reading your post, I get the additional benefits you’re wanting from having it in built that way. ---
**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\ **Post date:** [July 31, 2025, 6:19pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/10 "2025-07-31T18:19:59Z")
The Slack news sucks. WTF are they thinking there? ONE request per minute? ONE?? Although, I’d be curious to hear how the integration specifically impacts Fibery. For things like notifications (a task is completed, so it notifies a Slack channel), it seems like that sort of integration would NOT use the conversations.replies nor conversations.history API endpoint (the only endpoints affected, apparently). Would there be a way to maintain simple one-time notifications via the Slack integration while ditching any calls for the conversations history/reply endpoint? ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [July 31, 2025, 6:25pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/11 "2025-07-31T18:25:28Z")
Yeah, and embedding things into Rich Text is extremely time consuming, unintuitive and pretty janky on the best of days. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [July 31, 2025, 6:37pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/12 "2025-07-31T18:37:17Z")
> [@mdubakov](#): > > It means our Slack-to-Fibery sync can’t longer work. The best reason yet to add a first-class messaging system within Fibery 😀 Or maybe: [Open Source Slack Alternative | Mattermost](https://mattermost.com/open-source-slack-alternative/) ---
**Author:** ![Hendrik](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@Hendrik](https://community.fibery.io/u/Hendrik)\ **Post date:** [July 31, 2025, 9:18pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/13 "2025-07-31T21:18:55Z")
> [@mdubakov](#): > > context Dashboard Views Awesome! Thank you. > [@mdubakov](#): > > Scroll wheel zoom Thank you! Huge ‘quality of life’ improvement for me! Dashboard implementation is also good and enjoyable to use. ---
**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\ **Post date:** [July 31, 2025, 9:30pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/14 "2025-07-31T21:30:24Z")
Great improvements - thanks! ---
**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")
@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
 ---
**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\ **Post date:** [August 1, 2025, 12:40am UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/16 "2025-08-01T00:40:04Z")
Big +1 here – that would completely revolutionize the workflow & usability ---
**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:** [August 1, 2025, 7:47am UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/17 "2025-08-01T07:47:00Z")
> [@grex22](#): > > For things like notifications (a task is completed, so it notifies a Slack channel), it seems like that sort of integration would NOT use the conversations.replies nor conversations.history API endpoint (the only endpoints affected, apparently). Notifications are not affected, just fetching messages FROM Slack to Fibery. ---
**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:** [August 1, 2025, 8:18am UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/18 "2025-08-01T08:18:09Z")
> [@danielbmarsh](#): > > Alongside dashboards, I believe **entity context-based views** in Fibery deserve a major upgrade. Imagine an Account entity where: Overall I see no problems to make Context Views visible in Entity View as well where you can drag them as all other blocks (fields) and make Dashboard View on top, etc. We will think about it ---
**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\ **Post date:** [August 1, 2025, 2:57pm UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/19 "2025-08-01T14:57:56Z")
Ahh
 Ok, thanks for the clarification. I should’ve read that a bit more closely. That doesn’t impact our usage as much, but still immensely frustrating ---
**Author:** ![anon93347683](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@anon93347683](https://community.fibery.io/u/anon93347683)\ **Post date:** [August 5, 2025, 11:59am UTC](https://community.fibery.io/t/july-31-2025-context-dashboards-and-embed-widget-some-improvements/9316/20 "2025-08-05T11:59:02Z")
> [@mdubakov](#): > > Notifications are not affected, just fetching messages FROM Slack to Fibery. Just to confirm, does **“Receive instant data updates using webhook”** still work after the new Slack rate limits?