# šŸ¦­ Fibery Product Report: June 2025 **URL:** \ **Category:** News & Announcements\ **Created:** [July 7, 2025, 12:41pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145 "2025-07-07T12:41:54Z")\ **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 7, 2025, 12:41pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/1 "2025-07-07T12:41:54Z")
As usual, here is our internal product report for June 2025 šŸ§Š. Weā€™ve had 4 releases with 625 value points ( **440** ā†’ **400** ā†’ **625** last 3 months). ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/6e56cc59580ecdd620b01462a65254b68d111431.png) Main product areas and how they will change with time in near future. ![Screenshot 2025-07-07 at 3.20.14 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e90fa8c2b3d31f37417d46da3e239a499df7f04a.jpeg) ## Permissions ### Capability-based Space permissions We are (finally!) in the process of migrating to the new capability-based mechanism for Space access. At this point, nothing changes for the users, itā€™s purely an enabler for our next features. Okay, perhaps, Fibery will work slightly faster, especially for large workspaces, once we fully migrate. Most internal services already support the new mechanism, you can see the progress based on the Dev Tasks here: _Allow not to extend access from Space to its Databases_. The first two meaningful things after the migration would be: - _Allow to have Databases outside Spaces (in Default Space)_ - _Consolidate default access template names across Space, Database, and Entity levels_ ### Access audit Weā€™ve introduced access audit on Space and Database levels so that architects can tell who has what final access and why: - _Show all Users who have access to a Space_ - _Show all Users who have access to a Database_ ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2a9a70965efa61337ce3cc94c184f4bace3714d8.png) Next step: _Introduce access audit for Users and User Groups_ from the other side. ### Adoption Bad news first: it doesnā€™t look like those who have created but havenā€™t used custom access templates started to do so after _Explain access templates_: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4809a24b3ee9a71f0028e51acbd9fc345adb7bda.jpeg "The gap between created and used is still huge") Itā€™s no better for workspaces created after our changes went live (Apr 24): ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/95d5e6edd47334a25a2550852ed94b32ac073d34.png) Maybe, people are just exploring custom access templates šŸ¤·. Weā€™ll need a proper qualitative research (aka a few interviews) to figure out whatā€™s going on. Good news: 40% of all collaborative workspaces now utilize User Groups and automatic access via People Field while over 30% share Databases, both numbers higher than expected: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d0e0d38d8ed13037fb462b4b74eb4f38a4d7a4c9.jpeg) ## Import ### CSV Over 200 workspaces have used CSV import in the last 30 days which shows the demand, and quite a few customers have complained about its deficiencies which shows the room for improvement. So weā€™ll continue working on the CSV import till we (and customers) are largely satisfied. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/78d2115ac61d3080b705d9d305411b076ae22425.png) These were the two main things we delivered in June: - _Allow non-Admins to import data into existing Database_ - _Make switching from new to existing Field in integrations Field mapping discoverable_ And here are the next major candidates: - _Import self-related entities via a single CSV file_ - _Update existing entities via CSV import_ - _Introduce optional Field settings in integrations and import_ Additionally, it should be possible to import via the AI workspace builder. ### Discoverability A few small things: - _Suggest import or sync when adding a new Space_ - _Replace ā€œImport dataā€ with a nested ā€œImport fromā€¦ā€ menu_ - _Update headers for Database screens, including adding `Import` button._ ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/57cb781b3f032ea2e029290622dfde7eaf1bc75e.png) Weā€™ve postponed _Skip authentication method choice if OAuth is available for the connector_ until we find someone with Vizydrop expertise to join the import team. ### Notion After weā€™ve learned how to fetch rich-text from Notion, the next step is to _Sync Notion standalone Pages to Fibery Database_. Plus, make the connector stable. ### Duplicates Now architects can _Automatically merge duplicates when enabling unique toggle_: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/6093ac860198da49104923ee72ee44bddbd8c95c.png) The functionality is fully ready now, so weā€™ve started advertising it with the `New` badges. If there is enough demand, weā€™ll introduce a way to find and merge duplicates without requiring future values to be unique. ## Home page Weā€™ve released My Work widget and got immediate backlash in the community, since it is not flexible enough. This feedback came from mostly creators and it is unclear about its usage by mere mortals. We also did not promote it and did not make Home Page default (so far). Then we had a conversation and decided toā€¦ implement Dashboard View. Plan is this: 1. _Embed Views into Home Page with a dashboard-like layout_ 2. _Basic Dashboard View_ (it will support _Context Dashboard View_ as well as a result) 3. _Admins want to configure Home Page for other users_ So Kostya will spend July in these things. Behold! ![2025-07-07 15.29.03](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/dca2b65c5a409677562551d4b96529e96af3f9d3.gif) ## Gantt View Gantt View was released for Pro and Enterprise plans. It immediately became more popular than Map View and catching up with Thread View now šŸ¤£. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2c23b98b0cf57146b677144e9ed8674935525764.png) Weā€™ve made a serious mistake and based our Gantt View on board model, which lead to inability to show nested self-relationsā€¦ Now we are re-doing Gantt View to support List model, fixing some bugs and polishing it. Should be done in ~2 weeks. Then we will at least announce it in-product and see whether usage will be better. ## AI Weā€™ve released the first version of AI Build mode as experimental, and some accounts started to use it. Overall, usage is not so great, but it is growing, so there is hope. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1d4a4f08a81417bdc47b297329e5d742386d6394.png) AI Agent got new tools, like semantic search and Fibery user guide, so now it is more capable. Build mode has serious problems, since it can create databases with _corrupted_ schema. We hope to fix these problems in the first week of July and release new getting started experience in July. Other things we are working on: - _Add all views to Build mode (now it supports Table and Board only)_ - _Generate rules and buttons_ - _Make UI more pleasant with better context handling and artefacts_ ## Whiteboard In May, we released the first section updates and in June we kept improving them. You can now link and lock sections, and working with objects inside them is smoother. We also started improving how groups and selected objects behave. To better preserve data, we began updating the Undo history and will continue with Activity and Version History for whiteboards. What weā€™re working on now and planning next: - _Groups improvements_ - _Use arrow keys to move multiple selected items_ - _Make ā€œUndo/Redoā€ work well_ - _Whiteboard version history and activity_ - _Embed views into the whiteboard (reports, tables, etc)_ ![Screenshot 2025-07-07 at 3.41.11 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a9febed6dcf81b1f262a0284f31f4f062d24eb93.png) P.S. Your feedback is welcome! šŸ¦ā€ā¬› ---
**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 7, 2025, 12:42pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/2 "2025-07-07T12:42:06Z")
---
**Author:** ![Ryan\_Dejaegher](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ryan_dejaegher/32/8050_2.png) [@Ryan\_Dejaegher](https://community.fibery.io/u/Ryan_Dejaegher)\ **Post date:** [July 7, 2025, 1:18pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/3 "2025-07-07T13:18:26Z")
Dashboard view looks awesome! I know itā€™s possible to do this through columns and embedded views but this looks more intuitive and easier to layout. ---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [July 7, 2025, 3:33pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/4 "2025-07-07T15:33:38Z")
> [@mdubakov](#): > > So Kostya will spend July in these things. Behold! Looks awesome. The smoothest setup Iā€™ve seen so far for setting up a Dashboard like layout was with PostHog. Yours looks like it might end up even better ![shot_250707_182848](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/00e275c5015a4eb04b6985a132267bdcfe793845.png) ---
**Author:** ![Ryan\_Dejaegher](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ryan_dejaegher/32/8050_2.png) [@Ryan\_Dejaegher](https://community.fibery.io/u/Ryan_Dejaegher)\ **Post date:** [July 7, 2025, 5:42pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/5 "2025-07-07T17:42:52Z")
@mdubakov this is probably on the radar but just in case, [in this video](https://www.dropbox.com/scl/fi/cdoqxuysry9qmie1s43vl/CleanShot-Fibery_Fibery_2025-07-07-at-13.36.23.mp4?rlkey=szkdv1som33l61kq29m6m3vkd&dl=0) I talk about some bugs with the embedded whiteboard view ---
**Author:** ![Hendrik](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@Hendrik](https://community.fibery.io/u/Hendrik)\ **Post date:** [July 8, 2025, 1:46pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/6 "2025-07-08T13:46:02Z")
> [@mdubakov](#): > > Then we had a conversation and decided toā€¦ implement Dashboard View. Plan is this: > > 1. _Embed Views into Home Page with a dashboard-like layout_ > 2. _Basic Dashboard View_ (it will support _Context Dashboard View_ as well as a result) > 3. _Admins want to configure Home Page for other users_ This looks amazing! Thank you! Some questions: - Will this be available on all plans? - Will we be able to set up a Dashboard View for our clients (guests) that log in to a shared space? Would love to have a simple dashboard view where they can download the latest version of various document types (databases), see summary info etc. We would want to have one for different types of users which might have different data that is relevant to them. * * * > [@mdubakov](#): > > Embed views into the whiteboard (reports, tables, etc) Awesome! (Thank you!) ---
**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 8, 2025, 1:50pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/7 "2025-07-08T13:50:07Z")
> [@mdubakov](#): > > Then we had a conversation and decided toā€¦ implement Dashboard View. Plan is this: > > 1. _Embed Views into Home Page with a dashboard-like layout_ > 2. _Basic Dashboard View_ (it will support _Context Dashboard View_ as well as a result) > 3. _Admins want to configure Home Page for other users_ Amazing!!! Love the mockup, itā€™s exactly what I was hoping for. Instead of a special ā€œdashboard viewā€, is there reason why you wouldnā€™t just make the entire entity layout a flexible grid and then users can truly customize entities to their hearts content? ---
**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 8, 2025, 2:06pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/8 "2025-07-08T14:06:08Z")
> [@Hendrik](#): > > Will this be available on all plans? Yes, except Free > [@Hendrik](#): > > Will we be able to set up a Dashboard View for our clients (guests) that log in to a shared space? Would love to have a simple dashboard view where they can download the latest version of various document types (databases), see summary info etc. We would want to have one for different types of users which might have different data that is relevant to them. Dashboard View is just a View and nothing else. So it will work same way as Document with embedded views, for example. ---
**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 8, 2025, 2:07pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/9 "2025-07-08T14:07:06Z")
> [@interr0bangr](#): > > is there reason why you wouldnā€™t just make the entire entity layout a flexible grid and then users can truly customize entities to their hearts content? Fully custom entity view layout is MUCH harder to implement. Maybe someday we will do it, but not in near future ---
**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 8, 2025, 2:08pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/10 "2025-07-08T14:08:23Z")
> [@Ryan\_Dejaegher](#): > > I talk about some bugs with the embedded whiteboard view Thank you! Views in whiteboard is a very early preview with many problems, we will fix them till the release ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [July 9, 2025, 10:33am UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/11 "2025-07-09T10:33:57Z")
> [@mdubakov](#): > > Fully custom entity view layout is MUCH harder to implement. Maybe someday we will do it, but not in near future From what youā€™ve shared in the past it was due to having tricky ā€œDefaultsā€ for an dashboard layout of an entity. Maybe thereā€™s other reasons not shared. But having a dashboard layout (along with single and double columns) would be really amazing. It would start blank, and would just another entity view layout. No need for defaults. Iā€™m just worried you are making the same mistake you made with documents in the past. [Native documents vs. Documents database - #5 by mdubakov](https://community.fibery.io/t/native-documents-vs-documents-database/6323/5) Personally Iā€™d prefer taking the time to do it right, than rushing to do it in a way that will be harder to fix later. ---
**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:** [July 9, 2025, 10:36am UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/12 "2025-07-09T10:36:45Z")
> [@RonMakesSystems](#): > > Iā€™m just worried you are making the same mistake you made with documents in the past. [Native documents vs. Documents database - #5 by mdubakov](https://community.fibery.io/t/native-documents-vs-documents-database/6323/5) > > Personally Iā€™d prefer taking the time to do it right, than rushing to do it in a way that will be harder to fix later. Having ā€˜dashboard viewā€™ as an option for sidebar views does not stop us from developing ā€˜dashboard layoutā€™ as an option for entity view. They support different use cases. ---
**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 9, 2025, 6:22pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/13 "2025-07-09T18:22:09Z")
> [@mdubakov](#): > > ## Home page > > Weā€™ve released My Work widget and got immediate backlash in the community, since it is not flexible enough. This feedback came from mostly creators and it is unclear about its usage by mere mortals. We also did not promote it and did not make Home Page default (so far). > > Then we had a conversation and decided toā€¦ implement Dashboard View. Plan is this: > > 1. _Embed Views into Home Page with a dashboard-like layout_ > 2. _Basic Dashboard View_ (it will support _Context Dashboard View_ as well as a result) > 3. _Admins want to configure Home Page for other users_ > > So Kostya will spend July in these things. Behold! > > ![2025-07-07 15.29.03](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/dca2b65c5a409677562551d4b96529e96af3f9d3.gif) So glad you decided to go this way. I donā€™t tend to criticize because everything you do has some background data and evidence based decision with logic typical to Fibery and even if you go wrong way you check usage, feedback and then make the right decision. For me Home tab was something I would never use. Dashboards are way to go. Thank you! ---
**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 10, 2025, 7:47am UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/14 "2025-07-10T07:47:09Z")
> [@jandrabek](#): > > So glad you decided to go this way. I donā€™t tend to criticize because everything you do has some background data and evidence based decision with logic typical to Fibery We also do mistakes. A lot! ---
**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 10, 2025, 1:41pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/15 "2025-07-10T13:41:59Z")
Oh my god! I love dashboard view and Iā€™m surprised it came so fast. This is one of the best features ever I just love it so much I feel like crying šŸ˜ƒ ---
**Author:** ![Jan\_Bilek](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jan_bilek/32/12216_2.png) [@Jan\_Bilek](https://community.fibery.io/u/Jan_Bilek)\ **Post date:** [July 12, 2025, 8:52am UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/16 "2025-07-12T08:52:33Z")
We see the homepage as a key missing piece in Fibery. Our team often struggles to navigate the spaces that matter, and tthereā€™s no clear overview of what lives where. To work around this, we created a document called ā€œšŸ” Homeā€ to serve as our manual homepage with links to the most important views and documents. But itā€™s only partially useful since we canā€™t set it as the default for everyone. ---
**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 14, 2025, 3:45pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/17 "2025-07-14T15:45:17Z")
> [@Jan\_Bilek](#): > > But itā€™s only partially useful since we canā€™t set it as the default for everyone. Allowing scripts/API to access and modify the left sidebar (for any/every user/group) would provide a general way to address this kind of issue. But probably a better solution would be a UI for admins to define such customizations (for any/every user/group). ---
**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:** [July 14, 2025, 3:58pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/18 "2025-07-14T15:58:28Z")
> [@Jan\_Bilek](#): > > Our team often struggles to navigate the spaces that matter, and tthereā€™s no clear overview of what lives where. To work around this, we created a document called ā€œšŸ” Homeā€ to serve as our manual homepage with links to the most important views and documents. But itā€™s only partially useful since we canā€™t set it as the default for everyone. There is always a tension between companies where the admin wants to dictate what the non-admins see/do and other companies where non-admins want freedom to configure how their workspace looks/works. This is what led to the splitting of the sidebar into ā€˜Workspaceā€™ and ā€˜Personalā€™ (rigid vs freedom). If thereā€™s nothing in a userā€™s Personal section, then they should always land on the top-most view in the Workspace section of the sidebar, meaning your ā€œšŸ” Homeā€ document could be the default landing for everyone if you put it at the top of the default space. ---
**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 14, 2025, 4:08pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/19 "2025-07-14T16:08:23Z")
Perhaps a compromise would be to allow Admin to lock specific Workspace sidebar items, to ensure they always remain on top for certain users, regardless of user sidebar customization. Ideally this would allow an admin to specify for _which users/groups_ an item should be locked. ---
**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:** [July 14, 2025, 4:52pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/20 "2025-07-14T16:52:22Z")
> [@Matt\_Blais](#): > > Perhaps a compromise would be to allow Admin to lock specific Workspace sidebar items, to ensure they always remain on top for certain users, regardless of user sidebar customization. The ā€˜Workspaceā€™ section _is_ effectively locked by Admins. They have control over the default space. Non-admins cannot change the ordering of top-level items (but Creators can play around with ordering within spaces). [Next page](https://community.fibery.io/t/fibery-product-report-june-2025/9145.md?page=2)