# 🐢 Fibery Product Report: April 2025

**URL:** <https://community.fibery.io/t/fibery-product-report-april-2025/8794>\
**Category:** News & Announcements\
**Created:** [May 15, 2025, 12:35pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794 "2025-05-15T12:35:37Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**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:** [May 15, 2025, 12:35pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/1 "2025-05-15T12:35:37Z")

</div>

_Previously:_ [Product: March 2025](https://community.fibery.io/t/fibery-product-report-march-2025/8551)

We’ve made four releases in April. Total Highlights Score: **440** (for comparison, it was **310** in March).

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

Polina recorded a nice webinar, watch it to see all changes in action:

[![](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/24b0b2b441defa41a9ba808f3d959b2f04065917.jpeg "Fibery product updates — April 2025") ](https://www.youtube.com/watch?v=PxPKCmtynRc)

🦥 _My personal feeling is that in March and April we slowed down. On one hand, there were a lot of holidays and they affected the cadence. Also more people are working on long-term deliveries like AI experiments, Gantt Chart, etc. I hope we will speed up in May, we have to deliver faster._

Current and nearest future themes (with assigned devs):

 ![Screenshot 2025-05-15 at 3.32.48 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/82bbf29998743f44055f6c8ec7bf1a525dc33b6b.png)

## Import

April was about laying out the ground work:

- understanding the current integration UX and identifying ways to simplify it
- collecting the data to make informed decisions: Track integrations & import in analytics;
- Prepare Field mapping UI for relations to enable Support relation Field in integration import in order to Merge CSV and CSV 2.0 import;
- Allow only unique values in a Field has plenty of value on its own but also is a stepping stone towards Update existing entities via CSV import.

 ![Screenshot 2025-05-15 at 3.23.09 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/19bf9084fc5ab7ef7c6e27bd7e226598232242c1.jpeg)

In May, Ihar will join after his Table View side quest, so we’ll do more to Make import more discoverable.

## Permissions

Group sharing continues to gain adoption (e.g. 13%→ 21% of collaborative workspaces for DB sharing, 2%→ 4.5% for automatic sharing):

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

Meanwhile, Andrew is still transitioning Space permissions to the new mechanism, and other devs adapt their services accordingly. It’s been taking longer than we expected, but there are no major roadblocks.

We introduced a brand new UX for access templates. Over the next few months we’ll see if this helps with adoption, especially for newly created workspaces.

While Andrew is still busy, we’ll take a Feature from _Permissions scope 2025_ that is not core-heavy: _Manage everything User or User Group has direct access to_.

## Adding and updating data

We’ve finalized all this grand development with _Improve Entity creation when formula is used for name (or some fields are required)_.

Eugene switched to Import theme.

## Sidebar

No progress. The last piece we want to do is _Home Page_ in Fibery. I hope we will start it in May.

## Gantt View

Gantt View appeared more complex than we hoped and it seems we will need at least 3 more weeks to complete it. May release looks plausible, but maybe it will even slip to June. Gantt View Remaining features are vertical DnD, entities planning and quick add.

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

## AI

This field is moving forward very fast. New models, A2A protocol, MCP protocol, etc. It is very hard to keep up with the pace of changes. We had a slow start with Workspace Builder and progress was stalled in Smart Agent, so I hope in May it will be faster.

### Q&A Smart Agent

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

Almost no progress in April. We experimented with new LLMs, but Claude 3.7 still the best (but GPT 4.1 is close already). Kostas did not switch to UI, so what is remaining is still the same as one month ago:

In progress

- UI
- Chat history

Later

- Create new entities from the replies
- Automation rule to invoke Smart Agent
- [A2A](https://google.github.io/A2A/#/) protocol to remove Agents switcher

### Fibery Workspace Builder

Progress is very modest here. Aleh spent a lot of time on older space creator to unlock growth team and only recently started to work on new space creation flow. Serge implemented some initial features for views creation, but it is far from done.

Our next step is to have an agent that can create spaces and databases, modify these things and create views. In some form it should be ready next week and then we will see how good it is.

Max played with A2A protocol and implemented a prototype that works well. So we will use it as a router to agents (Smart Agent, User Guide Agent, etc). Agents granularity is an open question, but we will try to make Smart Agent as fat as possible and then we will see how to decompose it to smaller agents.

## Whiteboard

Viktor completed _Share whiteboard externally_ and moved to other areas.

Only Vadim is working on Whiteboard from development point of view, so we have few features in nearest future plans:

- Whiteboard: Sections improvements
- Embed views into the whiteboard (reports, tables, etc)

## Mobile

No serious progress was made in Mobile, only some design work.

P.S. Ask your questions and provide crazy ideas. 🐌

---

<div class="post-metadata">

**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:** [May 15, 2025, 12:35pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/2 "2025-05-15T12:35:55Z")

</div>



---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [May 15, 2025, 1:23pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/3 "2025-05-15T13:23:28Z")

</div>

Although April was “slow,” personally, I’m happy with the quality of the updates that were made. I’m partial to developers and good process so I’m biased here. But I don’t mind slowness when the features are thorough and effective.

However, I’ve been watching the roadmap and I’m noticing that improving entity layouts hasn’t made it to the list of priorities for the year. I know Fibery is younger and smaller than a lot of tools in the space, but I find that the older my Fibery workspace gets, the more I’m in need of solutions grouping fields visually (workflow management) and archiving, but not deleting databases that have become out-of-service.

The discussions may not have a lot of steam but I know these features will make a big difference for heavy users.

> [@Declutter the entity display by grouping fields in collapsible field groups](https://community.fibery.io/t/declutter-the-entity-display-by-grouping-fields-in-collapsible-field-groups/4603):
>
> Declutter the entity display by grouping fields in collapsible field groups. Currently the fields, especially many to many relation fields which cannot be hidden, are taking up a lot of space and is a big UX tension. In general, I see that users (including myself) work mostly with title and richt text content of entities. Although Fibery apears more structure oriented, day to day work with Fibery requires a lot of clicks and the fields are a big distraction. Drupal solved this also with the f…

> [@Archive Databases/Spaces without Deletion](https://community.fibery.io/t/archive-databases-spaces-without-deletion/8208):
>
> As companies grow and evolve some databases should become read-only and/or removed from day to day operations. How are people handling this right now? I often avoid creating databases in Fibery for small projects or project specific data because there is no way to “Archive” a database or space. Examples: When building a custom workspace for a client (in Notion or Fibery) I often map out fields and their functions. When working in Fibery I do this off platform, but I would have just created a…

---

<div class="post-metadata">

**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:** [May 15, 2025, 2:10pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/4 "2025-05-15T14:10:25Z")

</div>

Love to read these reports, as always.

Looking forward to Gantt View! Wondering, will the current timeline views be updated go gantt? Or will they be separate views?

> [@mdubakov](#):
>
> Meanwhile, Andrew is still transitioning Space permissions to the new mechanism, and other devs adapt their services accordingly. It’s been taking longer than we expected, but there are no major roadblocks.

This is something I’m also really excited for! Will public spaces also support this? Share only certain databases to public?

> [@mdubakov](#):
>
> so we’ll do more to Make import more discoverable.

One thing that was annoying some time ago is that only space creators could import data. I wanted to let the bookkeeper upload transactions without making them creator. Hopefully something can be done here.

Thanks for sharing the report!

---

<div class="post-metadata">

**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:** [May 15, 2025, 2:11pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/5 "2025-05-15T14:11:43Z")

</div>

> [@RonMakesSystems](#):
>
> Wondering, will the current timeline views be updated go gantt?

Gantt View will be a new View.

---

<div class="post-metadata">

**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:** [May 15, 2025, 2:49pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/6 "2025-05-15T14:49:31Z")

</div>

Love these updates, keep em coming 😃

> [@mdubakov](#):
>
> Whiteboard […] so we have few features in nearest future plans […]

Damn, Whiteboards don’t get that much focus it seems even though, and I will die on this hill, it’s one of the biggest differentiator from the competitors - at least in our case where we use it for system modelling and user flows.

It would be nice if we could at least get some feature parity with some of the normal views, such as showing compact cards, or being able to color them based on rules.

---

<div class="post-metadata">

**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:** [May 15, 2025, 3:05pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/7 "2025-05-15T15:05:30Z")

</div>

One more question!  
Will the new files field also have a new api/file retrieval method. I’ve found it quite tricky to send files anywhere outside of fibery using the api.

---

<div class="post-metadata">

**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:** [May 15, 2025, 3:10pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/8 "2025-05-15T15:10:20Z")

</div>

Couldn’t agree more, whiteboards is the secret weapon of Fibery. This morning I was working with plain stickies on a board. I took a few, converted them to tasks, and then linked them to an asset using the relationship arrow. All without leaving the whiteboard.

The thing I love most about the whiteboard is it gives you the freedom to work with items at any hierarchy and without needing to make relationships.

---

<div class="post-metadata">

**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:** [May 15, 2025, 3:42pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/9 "2025-05-15T15:42:59Z")

</div>

We’ve been looking forward to the following updates but it doesn’t seem like you mentioned them here… are they still actively planned/prioritized?

- [Multiple File Fields on Entity / Improved Files UI](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/8)

- [Smart Folder Improvements](https://community.fibery.io/t/february-27-2025-share-database-with-group-or-everyone-new-sidebar-copy-as-markdown-timeline-and-required-fields-improvements/8354/29)

- [Set default entity view based on field value](https://community.fibery.io/t/multiple-entity-views-automated-selection/7554/5)

- [A million different UI/UX improvement ideas](https://community.fibery.io/t/fibery-ux-ui-enhancements/8368)

- Mind Map View / Auto Mapping on Whiteboards

Is there another place you guys list what’s currently in development/next in backlog other than these informal product reports or the [public roadmap](https://the.fibery.io/@public/Public_Roadmap/Roadmap-Board-5974)? Often there will be features released or refinements that didn’t seem to ever be mentioned in the roadmap so I wish we had a more accurate idea of what was actively in development/close to release.

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [May 15, 2025, 5:01pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/10 "2025-05-15T17:01:39Z")

</div>

> [@mdubakov](#):
>
> ![Screenshot 2025-05-15 at 3.32.48 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/82bbf29998743f44055f6c8ec7bf1a525dc33b6b.png)

“Files field (start)” in June is to address [Improving the Files Field: Naming, Sharing, and Organization](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/), no?

---

<div class="post-metadata">

**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:** [May 15, 2025, 6:22pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/11 "2025-05-15T18:22:44Z")

</div>

> [@tycecycle](#):
>
> “Files field (start)” in June is to address

More than that. Preliminary list of problems is this:

 ![Screenshot 2025-05-15 at 9.22.28 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e90538d6e3a3367dd3e35e332b4598c8f443c314.png)

---

<div class="post-metadata">

**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\
**Post date:** [May 15, 2025, 6:31pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/12 "2025-05-15T18:31:47Z")

</div>

Hahaha let’s make files great for the first time! 😆

Great list! 😊 Good luck solving all those puzzles 🧩

---

<div class="post-metadata">

**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:** [May 16, 2025, 7:11am UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/13 "2025-05-16T07:11:44Z")

</div>

> Gallery view

This will be awesome. Glad to see it got such a high score.

---

<div class="post-metadata">

**Author:** ![Renato\_Carvalho](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/renato_carvalho/32/11001_2.png) [@Renato\_Carvalho](https://community.fibery.io/u/Renato_Carvalho)\
**Post date:** [May 16, 2025, 11:35am UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/14 "2025-05-16T11:35:57Z")

</div>

Gallery view 🙏🙏🙏

---

<div class="post-metadata">

**Author:** ![karthikk\_vijay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/karthikk_vijay/32/1220_2.png) [@karthikk\_vijay](https://community.fibery.io/u/karthikk_vijay)\
**Post date:** [May 24, 2025, 1:35pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/15 "2025-05-24T13:35:38Z")

</div>

is there plan to allow preview of files in reference links?

for ex., i [[entity a]] and it has multiple image files attached to it, can i see them directly where the reference is placed without needing to open the entity and then clicking on the file to open as separate tab?

This would make our lives so much more easier as we operate with a LOT of files!
