# 🐨 Fibery Product Report: September 2025

**URL:** <https://community.fibery.io/t/fibery-product-report-september-2025/9784>\
**Category:** News & Announcements\
**Created:** [October 10, 2025, 3:07pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784 "2025-10-10T15:07:20Z")\
**Posts on this page:** 20\
**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:** [October 10, 2025, 3:07pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/1 "2025-10-10T15:07:21Z")

</div>

In September we did 4 releases with total **310** points ( **470 → 280 → 310** last 3 months).

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

Main product areas and how they will change with time in near future.

 ![Screenshot 2025-10-10 at 5.50.10 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/372881799b3f80795dd40e3358950c6c1702f399.png)

## Permissions

### Manage public sharing

We now provide an option to review and restrict public sharing for security-sensitive workspaces:

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

- _Disable public sharing in a workspace is fully live._
- _See everything shared publicly_ is live with publicly shared Reports coming next.

The two scenarios (disabling future shares and auditing existing ones) go hand in hand, so we’ve decided to implement them together.

### Public sharing 🍻 access templates

While we are in the context of public sharing and Vova is available, we’ve decided to finally migrate the old entity public sharing mechanism to [access templates](https://the.fibery.io/@public/User_Guide/Guide/Custom-Access-Templates-240): Share Entity to web via a link using access templates.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a1cdc8938caf6e81814983f40ad6c5180cc3ca44.jpeg)

The old mechanism is sharer-dependant which makes it unpredictable (shared content depends on the sharer’s access) and undiscoverable (no one but the sharer can see that entity is being shared). It’s also approaching its scalability ceiling.

The new public sharing mechanism will mirror the regular sharing: a sharer selects what related entities to share by choosing the corresponding access template and everyone can see that an entity is being shared.

We won’t (over)share mentions or users anymore. We’ll start with using the new mechanism for new shares and nudging users to migrate old shares while preserving the URLs. In May 2026, we’ll mass migrate all the remaining old shares and retire the old service.

We expect the first release to happen in October.

### Space access

_Deleting v1 permissions model_ is done!

Now we proceed with the first customer-facing update: _Consolidate default access template names across Space, Database, and Entity levels_. Hopefully, the update is coming in October.

The first phase of _Deprecate old Contributor Space access_ is coming right after the consolidation.

_Allow not to extend access from Space to its Entities_ will be the next big thing.

We might also Introduce _custom access templates for Databases access_ if more demand will be there.

### Analytics corner 🤓

We’ve discovered the ceiling for permission-related functionality, 40% of collaborative workspaces 🙃:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/75d65bff272544b86ac48470091ba78c17c9f02c.jpeg)

Automatic access via People Fields, User Groups, Entity and DB sharing — everything has between 36% and 42% adoption rate now.

## Import

### Users 🍻 integrations

We’ve made the choice of how users are imported and synced explicit to help during the migration from other tools:

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

We’ve also added People Field support to the integration framework and then to a couple of popular connectors: Notion and Clickup. Other connectors (like Hubspot) will follow based on the demand.

Now you can sync a Person property from Notion into a People field in Fibery, making (gradual) migration smoother.

The long-overdue Update vizydrop styles to match Fibery UI are almost there.

### One-liners

Here are a few smaller things we’ve added or fixed:

- _Support Notion Databases with multiple Data Sources_
- _Apply Phone formatting for Hubspot and Intercom Contacts by default_

### Analytics corner 🤓

_Update existing entities or skip duplicates via CSV import_ has great adoption:

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

In the last 30 days, **25%** of all CSV imports have used one of our duplicate strategies, 260 Databases across 71 different workspaces.

### Next

We’ll pause Feature development for a while as Anton will be consumed by hiring, onboarding, and permissions.

_Import data into existing Database via integration connector_ is one important thing left from the initial plan.

The rest of the work is more on the product/content side: provide architects with all the (honest) info to help them choose between Fibery and other platforms and if (when?) they chose Fibery, help them migrate from their specific tool. This looks like something for November, unless pieces of it won’t be used as pilot projects for [potential designers](https://fibery.io/blog/we-are-hiring/brand-designer/).

## Usability and simplicity + New Enterprise Customer features

We’ve started working on features relevant for our New Large Enterprise Customer. Features are quite diverse. Overall, almost all New Enterprise Customer features are aligned with Usability & Simplicity theme, which is good,

### Live

Here is what we’ve done so far:

_Specify which Entity View to open based on some field value_ was released, but it has limited value for them, since they also want to hide some Tabs completely based on rules. So far we aren’t going in this direction, but will think about it.

We accidentally did _Rename “Name” field feature_, since AI already did that and we just had to allow it.

_Load only first N collection items for Collection Unit_ was implemented to speedup views in some cases.

Some minor UI and design improvements were added here and there.

### Next

Some filters and sorting improvements:

- _Quick Filters where users can change values_ + personal filters unification Here we want to improve and extend pinned filters and maybe even unite them with personal filters.

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

- _Reports: Add a toggle allowing viewers to browse source data_

- 🍭 maybe we will find time for _Generalize context filters into dynamic values_ in near future

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

Some automations things if we have time:

- _Duplicate automations to other databases_ will help people with faster rules setup
- or maybe even _Dynamic values in automations_ (Rules and Buttons)

Some random things

- _Batch drag and drop cards on Timeline & Gantt View_
- Ihar will finalize Board re-design and then focus on complex things, like _Use the same Database multiple times in Smart Folders & Lists & Tables_ 💪.
- Some features to simplify export will be completed, like _Export from Database setup screen_ and _Export from Grid & Lists: Export all the data and all levels, even collapsed_

Most likely some Users and security things will be done by Ilya:

- Service/Integration users
- Session lifecycle options

## Files field

Files was one of the most neglected area in Fibery. Files did not change after initial release abut 5 years ago 🧟. It is time to pay the debt and make them ~~good~~ great.

We’ve kickstarted _Multiple Files Fields per Database_ feature and working on it. It is quite vast, but should take less time than People field unification.

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

I’ve been thinking about making File a proper Database, but it seems we should wait till Core will be free and happy again, and maybe then we will start _Global Databases (Documents, Users, Tasks, Files, etc.)_. Then we will maybe migrate Files to proper entity, but not now.

Scope is nailed, and Eugene will soon join the team to work on fancy features.

### Next

Our goal is to make the first release is October and do Multiple Files Fields per Database with Support File Field in automations

Then the scope is:

- _File unit on Views with previews, add action_
- _Gallery View_
- _Download all files from entity with a single click_
- _Open/preview file instead of downloading it_

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/33a3a9e3ee5342fae9f87fab0669de45705a1aea.jpeg)

## AI

AI Agent adoption stalled. In September we had less calls to AI Agent than in August. Main complaint is that Fibery AI Agent is slow, so we are trying to address this problem in Build mode first.

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

Notion released AI Agents (Notion 3.0 in general). Notion AI works quite fast and nice, I don’t think we can catch up here with them. It does not mean we should not add AI builder, but it can’t be our competitive advantage for sure.

> **[The AI workspace that works for you. | Notion](https://www.notion.com/product/ai)**
>
> Build custom agents, search across all your apps, and automate busywork. The AI workspace where teams get more done, faster.

### Live

Not much. We’ve released _MCP for ChatGPT_

### Next

Now we are working on new version of AI Agent (Build mode only) that will be 2-3x faster and more scalable. Max is doing the main Agent stuff, while Serge is helping and completing Schema agent. I hope we will release something workable in October at least as a deep prototype.

- _Migrate Fibery AI to Multi-Agent system_
- _Schema agent v2_
- _Rules agent is also in development_, but there is hope we will have it in good shape in October

> Our first approach was to let Agent write code without any limitations. It is error-prone and quite slow. Our current approach is to narrow-down Agent capabilities somewhat, but make it way faster.

## Whiteboard

In September, we released an important feature _Whiteboard activity_ for the whiteboard: users can now see changes made in their absence and restore deleted objects from history. We also improved the behavior of bent connectors _Whiteboard: Bent connectors improvements_ for easier handling and reworked the text block functionality _Update text-box rendering_ and fixed a bunch of bugs.

**Activity**

#### Next

Vadim started working on embedding views into the whiteboard Insert views into the Whiteboard I’m working on templates and improving how relations function on the whiteboard.

- _Insert views into the Whiteboard_
- _Whiteboard: Templates_
- _Whiteboard: Support all relations_

## Mobile

We’ve updated the authorization flow and screens, redesigned the view toolbars for a smoother experience on mobile devices. Started testing certain features like notifications and editor, refining the main UI elements for the mobile view.

Our goal is to release the version with the current scope in two weeks for beta testers (we have 70+ people) and gather feedback and by the end of the month the first version will go to the App Store and Google Play.

 ![Screenshot 2025-10-08 at 10.24.06](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/45644ba90826824f793e781a19aa38c2b45ce978.png)

#### Features that need to be completed for the beta release:

- _Update Create new entity page_
- _Update Search on Mobile_
- _Update Home on Mobile_
- _Update AI chat on Mobile_
- _Update Inbox and Watchlist, Shared with me on Mobile_
- _Update inline comments in mobile app_

P.S. Feel free to share your thoughts and thank you for using Fibery 🧡

---

<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:** [October 10, 2025, 3:08pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/2 "2025-10-10T15:08:06Z")

</div>



---

<div class="post-metadata">

**Author:** ![Finanzamt\_Muellheim](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/finanzamt_muellheim/32/12892_2.png) [@Finanzamt\_Muellheim](https://community.fibery.io/u/Finanzamt_Muellheim)\
**Post date:** [October 10, 2025, 3:17pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/3 "2025-10-10T15:17:10Z")

</div>

What a Month (My first month btw) a big thank you to the whole team, you are creating art.

💪 **KEEP FIBERYING** 💪

---

<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:** [October 10, 2025, 3:33pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/4 "2025-10-10T15:33:49Z")

</div>

> [@mdubakov](#):
>
> Notion AI works quite fast and nice

Thinks fast, acts slow. Tried adding 200 sample items it did it one by one. Tried then updateing those 200, but because only 50 were loaded on screen it only saw 50 and only updated those… one by one…

Fibery: Thought for longer, acted much faster.

While adding sample data is niche, I do have a client that throws in meeting notes, and it makes all the tasks, so this in general about working with data in bulk. Fibery AI \> Notion AI.

> [@mdubakov](#):
>
> Generalize context filters into dynamic values

Exciting! Maybe using formulas…? Or even just the lookup arrow like with other filters “This PA \> Assignees”

> [@mdubakov](#):
>
> Files field

So looking forward to this one!!

> [@mdubakov](#):
>
> I’ve been thinking about making File a proper Database, but it seems we should wait till Core will be free and happy again, and maybe then we will start _Global Databases (Documents, Users, Tasks, Files, etc.)_. Then we will maybe migrate Files to proper entity, but not now.

Would love it to be a files database in some future, but also sharing thoughts that I’m scared of the “Global Databases”. Users and Files make sense as global as they are fundamentally different. But not all workspaces use Tasks or Documents, so having them as templates, and anyone can add or remove custom databases to global databases would be more ideal imo.

Also, maybe different workflows need files for different things, so you’d then have separate files databases for different use cases and relationships. Lots to think about

> [@mdubakov](#):
>
> I’m working on templates

If [whiteboard were fields](https://community.fibery.io/t/split-whiteboard-view-to-a-canvas-field-and-a-network-view/8687), you could have templating work in the same way as it does with entities. “Templates” database, and when entity linked to template, overwrite the the whiteboard field with the template’s whiteboard field data. I’m standing my ground on this one haha.

Whiteboards are getting more and more separate from the Fibery ecosystem and I’m worried it’ll be harder to bring them in later. Not sure where the data for the whiteboard templates will live…

> [@mdubakov](#):
>
> Mobile

Looking forward to this!! I think it will make it much easier to get buy in. I’ve heard it be a must-have a few times.

---

<div class="post-metadata">

**Author:** ![Eva\_Folch](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eva_folch/32/11814_2.png) [@Eva\_Folch](https://community.fibery.io/u/Eva_Folch)\
**Post date:** [October 10, 2025, 3:36pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/5 "2025-10-10T15:36:10Z")

</div>

Amazing! 👍

Dynamic filtering would be so useful! Formulas would be fantastic! Can’t wait! 👏

---

<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:** [October 10, 2025, 3:42pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/6 "2025-10-10T15:42:34Z")

</div>

Any words on the gallery view?

---

<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:** [October 10, 2025, 4:44pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/7 "2025-10-10T16:44:49Z")

</div>

We will start it this or next month. What do you want to know in particular?

---

<div class="post-metadata">

**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\
**Post date:** [October 10, 2025, 7:47pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/8 "2025-10-10T19:47:34Z")

</div>

The upgrades to files look great! And I’m excited that the mobile beta will be in a few weeks too! Thanks, team!

---

<div class="post-metadata">

**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\
**Post date:** [October 14, 2025, 9:41pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/9 "2025-10-14T21:41:27Z")

</div>

So happy to see files back on the agenda! Thank you for all your hard work

---

<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:** [October 15, 2025, 10:50am UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/10 "2025-10-15T10:50:06Z")

</div>

Status and ETA. I was worried it was put on hold but you clarified it. Thanks

---

<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:** [October 15, 2025, 11:04am UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/11 "2025-10-15T11:04:18Z")

</div>

Gallery View development should start early next week. Design is almost ready and File Field that it is dependent on should be released next week

 ![Screenshot 2025-10-15 at 2.03.52 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3eb6dae1b101213f6a5e94f00a612a6b0f7960e0.jpeg)

---

<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:** [October 15, 2025, 12:38pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/12 "2025-10-15T12:38:44Z")

</div>

Great!! Thanks for the update. Both the File Field and the Gallery View I can put to use straight away for many purposes.

---

<div class="post-metadata">

**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\
**Post date:** [October 15, 2025, 1:01pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/13 "2025-10-15T13:01:34Z")

</div>

Really awesome! Can’t wait to be able to add an image to an entity so that it shows as a cover image like in Notion.

---

<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:** [October 16, 2025, 7:49am UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/14 "2025-10-16T07:49:39Z")

</div>

Looks great.  
This will be a huge win for some particular use cases such as a catalogue of team members or contacts.  
In the future it would be nice to be able to group them by rows as well.

---

<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:** [October 16, 2025, 7:51am UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/15 "2025-10-16T07:51:11Z")

</div>

> [@Mircea\_Braescu](#):
>
> In the future it would be nice to be able to group them by rows as well.

This is already in scope

 ![Screenshot 2025-10-16 at 10.51.00 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e07d78758cc5499b69b305f527e8f4dcb40e9678.jpeg)

---

<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:** [October 16, 2025, 12:11pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/16 "2025-10-16T12:11:19Z")

</div>



---

<div class="post-metadata">

**Author:** ![Hendrik](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@Hendrik](https://community.fibery.io/u/Hendrik)\
**Post date:** [October 16, 2025, 4:30pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/17 "2025-10-16T16:30:17Z")

</div>

@michael, this looks great!. Any plans for adding previews like this for PDF documents as well? Also wondering if PDFs will also still get some love for whiteboards…?

---

<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:** [October 16, 2025, 4:44pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/18 "2025-10-16T16:44:55Z")

</div>

> [@Hendrik](#):
>
> Any plans for adding previews like this for PDF documents as well?

Yes, we are going to add preview for all basic and popular file types. Whiteboard is a different story and no immediate plans here, but we will see

---

<div class="post-metadata">

**Author:** ![Hendrik](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@Hendrik](https://community.fibery.io/u/Hendrik)\
**Post date:** [October 17, 2025, 8:11am UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/19 "2025-10-17T08:11:43Z")

</div>

> [@mdubakov](#):
>
> Yes, we are going to add preview for all basic and popular file types. Whiteboard is a different story and no immediate plans here, but we will see

Thanks Michael,  
It would be great if you could transfer at least some of that PDF love to the whiteboard. Regarding _basic and popular file types_, I would doubt that you have a single user that does not use PDFs on a daily basis. If cards could at least get PDF thumbnail previews (first page or user selected page or user selected image in pdf??) the way images do, it would be great if at least this function could be transferred to the whiteboard. I am (still) campaigning for the whiteboard… -\_\_-

Best,  
Hendrik

 ![FIBERY PDF LOVE](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5a84f168c188b065d8a4fe314da8e13828c006d2.png)

---

<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:** [November 20, 2025, 2:38pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/20 "2025-11-20T14:38:49Z")

</div>

> [@Hendrik](#):
>
> Any plans for adding previews like this for PDF documents as well? Also wondering if PDFs will also still get some love for whiteboards…?

Released today [November 20, 2025 / 🧑‍🎨 Gallery view, Open and preview files, Fibery AI: Build v2.0](https://community.fibery.io/t/november-20-2025-gallery-view-open-and-preview-files-fibery-ai-build-v2-0/10043)

[Next page](https://community.fibery.io/t/fibery-product-report-september-2025/9784.md?page=2)
