# šŸ“ Fibery Product Report: October 2025 **URL:** \ **Category:** News & Announcements\ **Created:** [November 7, 2025, 1:51pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971 "2025-11-07T13:51:59Z")\ **Posts on this page:** 14\ **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:** [November 7, 2025, 1:51pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/1 "2025-11-07T13:51:59Z")
In October [we did 5 releases](https://community.fibery.io/c/news-announcements/changelog/17) with total **600** value points ( **470 ā†’ 280 ā†’ 300 ā†’ 600** last 4 months). Releases quality and speed is decent in October, hope we are back on track. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f142197a3f8b6819408078017ebdae3bf0d22c78.png) Main product areas and how they will change with time in near future. ![Screenshot 2025-11-07 at 3.18.22 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8a4d28584a53f3e03aa0543ec2e889e99a43be2e.png) ## Permissions ### Public sharing via access templates The new entity public sharing using access templates is live šŸŽ‰: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/36fe6667a3630d6a8c5a0f6a1183ed0f2300790b.png) We also have a pair of new shiny guides: - [Share Entity to Web via Public Link](https://the.fibery.io/@public/User_Guide/Guide/Share-Entity-to-Web-via-Public-Link-439) - [Share Entity to Web (legacy)](https://the.fibery.io/@public/User_Guide/Guide/Share-Entity-to-Web-(legacy)-440) It turned out to be a pretty complex Feature with many edge cases, but Vova, Alexey and Kate wrestled it and pinned it to the ground. Surprisingly enough, we havenā€™t received complaints about mentions or assignees not being shared (yet). This is not because our customers donā€™t care about public sharing: they immediately noticed the Entity Views mess ([our oversight](https://community.fibery.io/t/october-30-2025-share-entities-to-web-using-access-templates-new-names-for-access-levels-improved-file-fields-support-in-automations/9924/14)): _Specify Entity Views for a publicly shared Entity_. In the best case scenario, we wonā€™t receive further major complaints and finish the planned scope in November: - _Allow to batch migrate old sharing links in Public Sharing settings_ - _Track entity public sharing in history_ - _Display publicly shared entities on access template page_ - _Check extra permissions when updating/deleting custom access template if itā€™s used in public sharing_ ### Space access Now that all the foundations are ready, the pace of customer-facing releases is great. All of these Features are now live: - _Consolidate default access template names across Space, Database, and Entity levels_ - _Deprecate old Contributor Space access_ - _Enable automatic Editor access via Created By by default for new Databases_ ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7eaa3b4de29364b480f38b2f7bf1afa85d4d0f15.png) And _Allow not to extend access from Space to its Entities_ is coming next. As for _Allow to hide Space data (entities) from Admins_, we decided to postpone it for now. The solution is still valid, but we have found much more vulnerabilities weā€™ll need to close than we had initially expected. Itā€™s mostly predictable no-innovation-needed work, but thereā€™s plenty of it. Weā€™ll identify more holes to cover in the background. ### Next This is our current plan for the major scope: 1. _Introduce custom access templates for Databases access_. No template management UI for now, API endpoints only. 2. _Configure access to Users_ 3. _Add create capability to access templates_ 4. _Allow to hide Space data (entities) from Admins_ We donā€™t expect to tackle anything else major unless we uncover a critical need for any key customer. Weā€™ll consider _Granular Access_ theme over at the end of this scope (it is taking us 3 yearsā€¦ šŸ„²) ## Usability and simplicity Mostly small improvements in various areas were completed, while we tried to design a proper solution for quick filters. ### Live - Weā€™ve unified export and made it consistent on all views - _Export from Database setup screen (ā€¦ action)_ - _Export from Grid & Lists: Export all the data and all levels, even collapsed_ - _Export from Timeline, Gantt, Calendar Views_ - Some Views improvements, like Board View got several updates, including - _Make column separation more obvious_ - _Duplicate several selected entities_ - Some improvements on Entity View: - _Nice unification here Make Multiple Entity Views more discoverable_ - Self-driven initiative from Pavel: _Better drag and drop on Entity View_ - _Allow disabling linking existing Entities on a Context View (always create new Entities)_ - And totally unexpected Thread View update from Konstantin: _Make Threads status cross-device (read once, read everywhere)_ ### Next _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. It was a very painful feature to design and I only hope Pavel will be OK after its implementation. Complex shit! ![Screenshot 2025-11-07 at 3.42.18 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/224838c6f04369389556f8c12618f284392e1d61.png) Then we will jump to _Hide Entity Views based on rules._ It will be possible to setup a rule to hide Entity View from users. Most likely Misha will have to take it after Gallery View (or Pavel after Quick Filters, if he keeps his sanity) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/149340f25da23dca439f041d0401f37562342fc8.png) Other things that we want to do in November by brave and fearless Ihar - _Hide ā€œNo parentā€ group in multi-level Smart Folders/Tables/etc (when empty)_ - _Have own columns for nested items and do not merge columns to include more fields without changing width_ - this feature is missed by every Targetprocess customer šŸ™‚ ## Integrations Unexpectedly some work was done for Integrations by Misha (and expectedly by Eugene). - The most notable is _N8N integration_, but we are still waiting for the official approval. - _Discourse Webhooks support_ is also a nice small addition, now we get feedback items in Fibery fast. - People field support was extended: _Support People Field in HubSpot_ and _Support People Field in Intercom_ - Notion integration got improved by _Support Notion Databases with multiple Data Sources_ and _Fully support People Field in Notion integration_ ### Next We have no plans for this area for November. ## Files field Weā€™ve had great progress with Files field in October šŸ˜. Major base feature was released _Multiple Files Fields per Database_ and we also released several supplementary features: - _Download all files from file field and from entity_ - _Add possibility to filter by comments and file(s) with option is empty and non empty_ - _Support File Field in automations_ Feedback is good. ### Next Now we are working on the next significant things: _Open/preview file instead of downloading it_ ![Screenshot 2025-11-07 at 3.43.23 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8444eb649692266a869e0f2e2e2ca90fa0919d2b.jpeg) and _Gallery View_ https://www.loom.com/embed/0c4db5f692ac4073b9160e3605cd23de Then the future scope is: - _File unit on Views_ - _Rename file_ - ā€¦ and that is it. Maybe we will do some other features here as well, but so far no plans and we are going to stop there likely in December. ## AI We are still working on new version of AI Agent (Build mode only) that will be 2x faster and more scalable. Max is doing the main Agent stuff, while Sergey is helping and completing Schema agent. Release is close. I hope we can deliver something in 1-2 weeks. Overall, build mode works faster and more consistently, but visually you will not see any differenceā€¦ ![Screenshot 2025-11-07 at 3.34.53 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8b8991fce4ac26c61012de3b84191fd60844e423.jpeg) ### Next Aleh got some pause, got back and decided to work on _Create a Report with AI_. Reports are hard to create manually, so maybe we will have more success with AI here. We also want to make Views agent more consistent and see what we can do with various AI menus. We have to unify this in nearest future. ## Automations In November we will start several improvements in Automations. Small team Sergey + Eugene is formed and weā€™ll start doing something in a week or two. Our goal here is make automations good enough. It means resolve many major problems, but we are not going to re-write automations from scratch. **Evolution only**. - _Unite ā€œEntities linked/unlinkedā€ triggers with Entity Update trigger, allow to mix all fields via OR condition_ here we are going to simplify rules setup and make triggers more powerful - _Duplicate automations to other databases_ - _Access the previous value for Rules_ Future scope _maybe_ is: - _Use single-select options in automation Formulas_ - _WYSIWYG editor instead of plain text templates in automations (aka replace markdown editor)_ - _Automation Action: Post to Webhook_ Then we will see. This area will be continued till Q2 2026 at least. ## Whiteboard After we improved undo and added activity tracking, Vadim and Alex switched to enhancing Whiteboard-Fibery integration. Our goal is to make working with data and relations smoother and to add basic templates so itā€™s easier to get started with the whiteboard. Next week, weā€™re rolling out a big feature _Insert views into the Whiteboard_ that lets you embed or add views and documents directly to the whiteboard and support for embedding external resources, like YouTube videos or pdf. Widgets now support three modes: as a widget (fully interactive), as a mention or as a simple text link. You can build flows, group widgets into sections, and create quite complex dashboards. ### Next Our next step is improving relations on the whiteboard, adding support for read-only relations, formulas, and some visual enhancements for relations. Weā€™re also adding a new panel to make it easier to work with elements, including components for diagrams, new icons, and stickers. - _Whiteboard: Support all relations_ - _Whiteboard: Templates_ - _Add Picker for Icons, Emojis and šŸ¦„šŸ¦„ Stickers_ ## Mobile We released an internal version within the company (thanks to everyone who tested it šŸ«¶ ) and next week weā€™re rolling out the **external beta** for iOS/Android. For now, weā€™ve limited the scope since Dima ran off to work on permissions. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2b681132e9e646367b1a721f1dfb2a68c322fef6.jpeg) ### Next After the beta release we will be collecting feedback and improve current mobile interface (thereā€™s still a lot of work to do there) and getting ready for the first release. P.S. Your feedback, hearts, souls and punches are 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:** [November 7, 2025, 1:52pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/2 "2025-11-07T13:52:27Z")
---
**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:** [November 7, 2025, 2:18pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/3 "2025-11-07T14:18:00Z")
Yay for public sharing via access templates! Super happy about the files fields improvements and N8N integration (still trying to grab time to re-spin up a new N8N self-hosted instance). Sad about this ā€“ weā€™re holding off on expanding bringing in associates until this happens: ā€œAs for Allow to hide Space data (entities) from Admins, we decided to postpone it for now. The solution is still valid, but we have found much more vulnerabilities weā€™ll need to close than we had initially expected. Itā€™s mostly predictable no-innovation-needed work, but thereā€™s plenty of it. Weā€™ll identify more holes to cover in the background.ā€ Hopefully wonā€™t be put off too long. Looking forward to AI improvements. I was able to successfully automate a pretty tedious workflow (automatically gathering up all outstanding invoices from a single vendor and creating a single payment) using script via AI. Exciting! ---
**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:** [November 7, 2025, 2:27pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/4 "2025-11-07T14:27:29Z")
> [@timothy](#): > > weā€™re holding off on expanding bringing in associates until this happens Is this because your associates all need to have Admin/Architect capabilities? Or is your need related to hiding user data from other users? ---
**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:** [November 7, 2025, 2:39pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/5 "2025-11-07T14:39:09Z")
Hiding user data (avoiding unnecessary disclosure of confidential information to admins) ---
**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:** [November 7, 2025, 2:42pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/6 "2025-11-07T14:42:40Z")
Specifically hiding data in the User db? Or hiding entities in other dbs from the Admin(s) ? To be clear, the feature called `Allow to hide Space data (entities) from Admins` relates to hiding entities in non-User dbs. We have a separate feature to allow access to User info to be configurable. ---
**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:** [November 7, 2025, 2:57pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/7 "2025-11-07T14:57:34Z")
Outside the user DB. The idea is to be able to provide a software for IP project management, but not allow admins to see the professionalsā€™ data in the network-wide databases. The only other approach I know of now is to build a template, but most of the professionals donā€™t want to have to manage and update / migrate as templates change. ---
**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:** [November 7, 2025, 3:19pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/8 "2025-11-07T15:19:05Z")
Thank you for doing files! You have such great momentum, itā€™s really impressive ---
**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:** [November 7, 2025, 3:23pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/9 "2025-11-07T15:23:32Z")
You guys are amazing! Lovely month of updates. > [@mdubakov](#): > > (it is taking us 3 yearsā€¦ šŸ„²) So worth it though! > [@mdubakov](#): > > Access the previous value for Rules Super interested to see what will be possible with this! > [@mdubakov](#): > > WYSIWYG editor instead of plain text templates in automations (aka replace markdown editor) Personally I would much perfer something like this: [Rich text to Markdown with relations in automation](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289). My goal is to leave as much content outside of automations, and into entities, then use those entities as the templates. This allows granular control on who can edit what, and doesnā€™t require someone to be an architect in order to edit the email template. The exception to this is when using the ā€œAsk Userā€ on a markdown field. The alternative is to have them make a new entity, and have the automation get triggered on creation. The upside of this is that it could be set up as a draft, and only send when the user presses ā€œSendā€. Not sure of how it could work exactly. But just some ideas! * * * Super excited for all the things coming!! Files, access, mobile, thereā€™s just to much good stuff coming. Thank you all for putting your love and energy in this product! ---
**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:** [November 7, 2025, 9:03pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/10 "2025-11-07T21:03:09Z")
> [@mdubakov](#): > > week weā€™re rolling out the **external beta** Does it mean that users who signed to the form will have access? šŸ™‚ ---
**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:** [November 8, 2025, 8:52am UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/11 "2025-11-08T08:52:14Z")
> [@mdubakov](#): > > Hide Entity Views based on rules Very nice surprise! Iā€™m all for reducing clutter for our users! > [@mdubakov](#): > > _Open/preview file instead of downloading it_ Looking forward to this too! > [@mdubakov](#): > > next week weā€™re rolling out the **external beta** Woot! Iā€™m ready! ---
**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 8, 2025, 9:21am UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/12 "2025-11-08T09:21:51Z")
> [@RonMakesSystems](#): > > Personally I would much perfer something like this: [Rich text to Markdown with relations in automation](https://community.fibery.io/t/rich-text-to-markdown-with-relations-in-automation/8289). In fact it is the same, if we will replace current markdown we will add fields and templates to rich text as a solution. So same thing ---
**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:** [November 10, 2025, 7:00pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/13 "2025-11-10T19:00:29Z")
> [@mdubakov](#): > > Hide Entity Views based on rules Love this approach. Will this allow for rules based on the User as well as the Entity? User based filtering will also extremely helpful. ---
**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 10, 2025, 7:01pm UTC](https://community.fibery.io/t/fibery-product-report-october-2025/9971/14 "2025-11-10T19:01:21Z")
> [@danielbmarsh](#): > > Love this approach. Will this allow for rules based on the User as well as the Entity? User based filtering will also extremely helpful. Absolutely, based on logged user and her attributes.