# šŸ  Fibery product report: February 2026 **URL:** \ **Category:** News & Announcements\ **Created:** [March 9, 2026, 12:36pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513 "2026-03-09T12:36:18Z")\ **Posts on this page:** 16\ **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:** [March 9, 2026, 12:36pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/1 "2026-03-09T12:36:18Z")
# Product: February 2026 In February [we did 4 releases](https://community.fibery.io/c/news-announcements/changelog/17) with total **470** value points ( **530 ā†’ 820 ā†’ 480 ā†’ 470** last 4 months). ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9533b4f66931d78b085752df96a91a1100c3b036.png) In this report we will try to focus on strategic themes, not on product areas. Overall, weā€™ve released many good things in February and tried to focus on our themes with OK success. Still there is area for improvements! Product scope for the future was corrected. In short, weā€™ve replaced ā€œSupport many use casesā€ theme with ā€œMake AI Agents happyā€ theme. ## Theme: Granular Access ### Done _Allow non-Admins to manage webhooks_ was done. ### In progress Weā€™ve faced _Canā€™t hide some Fields from certain Users (aka per-Field read permissions)_ limitation quite a few times recently, and the most common workaround (slicing a DB into two) doesnā€™t work well because of Lookups. So we took _Show and edit related Entity Fields without a Lookup_: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/05c261177a0260a04b0163bdf9d7420d00956acf.png) If things go well, this functionality should make our relations even more powerful as well as simplify the life of Architects. ### Next Still waiting for Andrew to get to _Configure access to Users_ā€¦ ## Theme: Simplify Fibery for architects ### Done We improved import in _Introduce optional Field settings in integrations and import_ and worked on AI-assisted workspace setup mainly in February. _Create/Update a Report with AI_ was released, but not much feedback so far. Automations rules got previous values access as well: _Access previous values for rules in trigger filters, actions (via formula) and markdown templates_. ### Started or Planned for March Set context for AI is still in progress and we hope to finalize it in March. It will help architects to work on rules and formulas, create new objects better and forget about Ask/Build mode switcher. There are chances we will complete it indeed in March. - _Set context for Formula Field, update field when iterating with AI_ - _Support AI context for Automation Rules and Buttons_ - _New Objects creation from AI Agent unification_ - _Search Spaces_ - we need this for AI context - _Set AI context for Space_ - _Ask/Build mode removal_ _Redesign Database: Data header_ it is planned that Ihar will take this quite small feature to reduce architects confusion. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5fda02a477ad8794000f67d28e0555169af541c8.png) _Automatically link entities: operators besides = (\>, \<, ā‰ , ā€¦)_ and other auto-linking features. Sergey will lead this feature and area, while Eugene will execute. _AI Integration Agent: Create, test and deploy integration for customer via chat_. Now Oleg is working on a crazy idea to let architects create own integrations without code in Fibery. It already works, here is sync with Telegram created with several prompts and iterations. Maybe we will release it in March. https://www.loom.com/embed/11da3a475354492dbcc1da3d89fbcc95 ## Simpler workspaces toolkit ### Done Weā€™ve completed and finalized validation rules _Support Previous field values in validation rules_ and completed pinned filters _Pinned Filters where users can change values. Both features are very valuable_. ### Started or Planned for March We will complete several very useful things for entities: _Hide Entity Views based on rules_ _Specify which Entity View to open for a user or a group_ _Validation rules on Create events_ Customers are happy, but: > Iā€™m thrilled! Both about the hide tabs and the validation rules on create!!! Thank you! I realize itā€™s a bit cheeky to ask, but I have to ā€” are you also planning to add hide rules for fields? Or for buttons? If Dima will have time till permissions, we will do _Filter and sort relation selectors in Form View_. ## Theme: Make AI Agents happy ### Done Nothing. ### Started or Planned for March We are taking this theme instead of ā€œmany use casesā€ theme. There will be several areas of immediate improvements. - _Migrate tools from our Agent to MCP_. Here we will power up our MCP with many tools and experiment with it in the wild and _Support MCP for many sources (n8n, etc)_ also in scope. - _History API_. It will be released as a separate API, as a tool in MCP and there is hope that Trash and Audit Log will work faster as well. - _Make user guide AI-friendly_. Now ChatGPT and Claude do not see Fibery User Guide content. We will fix that. - _Better public API guides_. Sergey will lead this initiative to its conclusion and we will have better docs in better format for developers (and agents) to use. - _Better search_. Here we will focus on Search and Semantic Search improvements. Pavel will start something, then we will see who will join. ## Theme: Growth ### Done _Introduce themes to support new visual identity_. We released warm theme consistent with the new Fibery visual identity and made it default for new users: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2e77cc7d4c55977796faaa09de500f89dcaf355a.jpeg) The feedback has been (almost) exclusively positive so far: > One would imagine that this did not matter, but honestly as somebody who has always set a warm background in designs, I ā¤ā¤ā¤ it. Instant upgrade of my daily experience in Fibery. > > ā€” > > I love the warm theme! Really looks nice. I often use dark mode but this is also pleasant on the eyes. Itā€™s a fresh, warm look! šŸŒž ### In progress There are a few more things we need to polish to graduate the warm theme from beta and advertise it among the existing users: - _Apply custom theme in vizydrop reports (& import from CSV)_ - _Apply themes to desktop app_ - _Adjust color palettes based on theme_ ## Other This theme contains features that are **not part of our strategy**. However, for some reason, there are many features here. The reasons are stated below and overall this section should be as empty as possible šŸ˜¬. Some features are customer specific, sometimes we want to delight people. ### Done Many people worked on things outside our main themes due to various reasons. Dima did not have work from permissions and had to find something. Eugene is too fast and had time to work on several things in parallel. - Timeline: improve performance to support lots of items - Embed Fibery as an iframe into external applications - Filter by to-many relation count - Allow to pick multiple values in ā€˜containsā€™ filter in case of many-to-many relation - Batch drag and drop cards on Timeline, Gantt View, Board and List Views - Entity history for a specific Field - Empty states on Entity View - One-Click Copy URL from Table View (List, Board, Timeline too) - Prettify Form creation modal - GitHub: sync Projects - GitLab: Sync milestones from Issues - Add toggle to show/hide formula data in activity log and entity history AI Agent. Here we did many things for AI Agent it it was all in scope of our strategy. AI Agent quality improved, it gets mentions now, can access history, etc. - Stop AI Agent execution - Set AI context manually via UI control - Add ability to see history for AI Agent - AI Agent: Support mentions in rich-text - Re-design AI Panel Files. A continuation of files theme, still not done in February. - More File Unit visualizations on Entity View - File Unit visualization in Forms Whiteboard - Redesign shape toolbar ### Started or Planned for March Rich text product area polishing will continue: - _Improve pasting a markdown content form vs code editor_ - _Migrate mentions when converting or merging entity_ - _Reorder rich-text blocks via dragā€™nā€™drop and keyboard_ ![2026-03-09 10.54.29](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8802bbc3b5e4c50ec8b1d614e6ae2cc1d5cc4ef9.gif) Files. We have to finalize this theme. - _File Unit visualizations on Table View_ - _Sort files_ - _? Upload several files/images/videos at once_ Make Customer X happier. They create AI reports often but there is no place to show them in Fibery in a good way. _Create HTML reports in Smart Agent with Fibery (or custom) styles_ and _Embed View (iFrame View)_ ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/33fa7b4ad4b90505260c5e6e5594b927336cf7aa.png) Make Customer Y happier. _Create personal Folders in Favorites_. looks like a quick task for Kostas, that we will do after colossal DnD in rich edit. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1a68befb461e2c708e16cfd6e2b8e7e1ecd530f3.png) Make Customer C happier. _Add the ArchiMate shape set_. 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:** [March 9, 2026, 12:36pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/2 "2026-03-09T12:36:28Z")
---
**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:** [March 9, 2026, 1:04pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/3 "2026-03-09T13:04:49Z")
Thanks for sharing these, as always! > [@mdubakov](#): > > So we took _Show and edit related Entity Fields without a Lookup_: This sounds really amazing!! Essentially solving this: [Editable Lookup Fields](https://community.fibery.io/t/editable-lookup-fields/8424) As well better control over permissions. IE: only show the lookup if you have access to the other entity where that field is from. Opens up a lot of power!! I wonder if this could be set by formula? Get field x if a, and get field y if b. Of course, both fields must return the same type of data. It maybe would also allow going deeper into relations using a single field. > [@mdubakov](#): > > If Dima will have time till permissions, we will do _Filter and sort relation selectors in Form View_. Amazing!! Thank you Dima! This was a great month, looking forward to the rest March. ---
**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:** [March 9, 2026, 3:49pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/4 "2026-03-09T15:49:11Z")
Are the following things from your 2026 strategy still on your Q1-Q2 roadmap? **Every single one of them would be insanely valuable to us** so weā€™re anxiously waiting. šŸ„ŗ - Generalize context filters into dynamic values. Greatly simplify context management for views. - Allow users to create multi-relations (Polymorphic relations). For example, you want to link Document to Project, Epic or Feature, now you have to create three relations, and it is very bad workaround. - Automatically link entities: operators besides = (\>, \<, ā‰ , ā€¦). Now we have only = operator and it is not enough for many use cases. - Better Formulas (combine collections and entities, Convert Text to Number in Formulas, Clear field value in formula, ā€¦). ---
**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:** [March 9, 2026, 4:04pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/5 "2026-03-09T16:04:27Z")
> [@interr0bangr](#): > > Generalize context filters into dynamic values. Greatly simplify context management for views. Gonna start in March > [@interr0bangr](#): > > Allow users to create multi-relations (Polymorphic relations). For example, you want to link Document to Project, Epic or Feature, now you have to create three relations, and it is very bad workaround. Q4 in best case scenario > [@interr0bangr](#): > > Automatically link entities: operators besides = (\>, \<, ā‰ , ā€¦). Now we have only = operator and it is not enough for many use cases. Will be started this week. > [@interr0bangr](#): > > Better Formulas (combine collections and entities, Convert Text to Number in Formulas, Clear field value in formula, ā€¦). Most likely Q3 and Q4 ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [March 9, 2026, 4:19pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/6 "2026-03-09T16:19:19Z")
> [@RonMakesSystems](#): > > only show the lookup if you have access to the other entity where that field is from. Yep, this is a part of our thinking! > [@RonMakesSystems](#): > > I wonder if this could be set by formula? Get field x if a, and get field y if b. Of course, both fields must return the same type of data. It maybe would also allow going deeper into relations using a single field. For now, itā€™ll be straightforward one extra level deep without forking. Weā€™ll see what use cases pop up next. However, itā€™ll be a tradeoff between flexibility and performance, since those units have to be queried every time user loads a View with them. ---
**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:** [March 9, 2026, 4:42pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/7 "2026-03-09T16:42:46Z")
> [@mdubakov](#): > > Generalize context filters into dynamic values. Greatly simplify context management for views. - Gonna start in March Awesome! Any hints as to the scope? Iā€™m kinda hoping some the following might be addressed as part of it: - Allow entities from the same database to be added to a view at more than one level - Apply context filtering to all levels of hierarchy in a view, not just the top database - Fixing the UI on relation context filters where it becomes almost impossible to use if thereā€™s many levels due to how many options are listed. - In relation views, allow ā€œis this entityā€ value to used in filtering - In relation views, allow the ā€œis this entityā€œ value to be inherited by filters when creating new entities - Allow dynamic/context filtering on ā€œmany-to-manyā€ relationships - Allow dynamic/context filtering on ā€œto-oneā€ relationships - Allow ā€œto-oneā€ related databases to be displayed as levels in table/list views - Allow ā€œto-oneā€ relation to be displayed as ā€œrelation viewsā€, not just ā€œcompact listsā€ ---
**Author:** ![Bronn](https://avatars.discourse-cdn.com/v4/letter/b/b5a626/32.png) [@Bronn](https://community.fibery.io/u/Bronn)\ **Post date:** [March 10, 2026, 12:30pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/8 "2026-03-10T12:30:55Z")
> [@mdubakov](#): > > _Automatically link entities: operators besides = (\>, \<, ā‰ , ā€¦)_ and other auto-linking features. Sergey will lead this feature and area, while Eugene will execute. This is going to be huge. > [@mdubakov](#): > > are you also planning to add hide rules for fields? Or for buttons? +1, otherwise we will end up with many views with only 1-2 fields difference. > [@mdubakov](#): > > Filter and sort relation selectors in Form View Will this be based on what weā€™ve selected above in the form? Like, weā€™ve selected the project, so now we can choose a task associated with that project and donā€™t have to work out which we need. This would solve so many use cases for me because Iā€™m currently having to build stuff out with the caveat of ā€˜create the entity, but only with these details, ignoring this field that I canā€™t hide because itā€™s used in the name formula, then open the entity and now you can fill in that field because it finally has filteringā€™. Not so user friendly. šŸ˜… * * * I also wanted to ask, is smart folder context view still the only currently way to give context to a dashboard? I wanted to use a view for leads/projects so I could pin filters, but I want a dashboard for each, so itā€™s going to have to be a smart folder instead and with the number of leads and projects we have open at any one time (~400-500), this will get overwhelming quickly (not to mention that we sometimes want to look at the dashboard of a completed project to inform our choices on a current project). ---
**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:** [March 10, 2026, 12:43pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/9 "2026-03-10T12:43:39Z")
> [@Bronn](#): > > itā€™s going to have to be a smart folder instead and with the number of leads and projects we have open at any one time (~400-500), this will get overwhelming quickly Could you use filtering on the smart folder to prevent your sidebar from getting bloated? ---
**Author:** ![Bronn](https://avatars.discourse-cdn.com/v4/letter/b/b5a626/32.png) [@Bronn](https://community.fibery.io/u/Bronn)\ **Post date:** [March 10, 2026, 12:52pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/10 "2026-03-10T12:52:30Z")
> [@Chr1sG](#): > > Could you use filtering on the smart folder to prevent your sidebar from getting bloated? There are some people who need to access the dashboard of any and all projects. I considered adding multiple smart folders for different use cases, but I think that just adds to the problem. ---
**Author:** ![Tommy\_Hedley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tommy_hedley/32/6468_2.png) [@Tommy\_Hedley](https://community.fibery.io/u/Tommy_Hedley)\ **Post date:** [March 10, 2026, 1:52pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/11 "2026-03-10T13:52:36Z")
> [@mdubakov](#): > > > [@interr0bangr](#): > > > > Allow users to create multi-relations (Polymorphic relations). For example, you want to link Document to Project, Epic or Feature, now you have to create three relations, and it is very bad workaround. > > Q4 in best case scenario Dang, definitely had my hopes up about this one happening in Q2 šŸ˜”. Hopefully we can see it this year, one of my top desired features for a few years now. ---
**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\ **Post date:** [March 10, 2026, 3:13pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/12 "2026-03-10T15:13:31Z")
> [@Tommy\_Hedley](#): > > definitely had my hopes up about this one happening in Q2 šŸ˜”. Hopefully we can see it this year, one of my top desired features for a few years now. 100%. Waiting with excitement! Right now we need junction tables like this theoretic one to connect context to a work item (task): ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3aedd20bcaf363fceb168faba2a83a02d7c476df.png) Where as with Polymorphic Relations, if we need a junction table to hold junction attributes, it would be still much more compact with only one Polymorphic Object field, and if not need for junction attributes, then it would just a a field directly on the Subject Entity. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [March 11, 2026, 5:02am UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/13 "2026-03-11T05:02:24Z")
> [@interr0bangr](#): > > Allow users to create multi-relations (Polymorphic relations). For example, you want to link Document to Project, Epic or Feature, now you have to create three relations, and it is very bad workaround. yes this remains huge for me as well! ---
**Author:** ![Alex\_Rublev](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex_rublev/32/10881_2.png) [@Alex\_Rublev](https://community.fibery.io/u/Alex_Rublev)\ **Post date:** [March 13, 2026, 8:13am UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/14 "2026-03-13T08:13:46Z")
> [@mdubakov](#): > > Weā€™ve faced _Canā€™t hide some Fields from certain Users (aka per-Field read permissions)_ limitation quite a few times recently, and the most common workaround (slicing a DB into two) doesnā€™t work well because of Lookups. I didnā€™t quite understand what the issue is with separating the DB and Lookups. I thought this was a valid approach: we keep all fields in one database, and from the second one we only pull in the fields that the user should see via lookups. Could you please clarify? ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [March 13, 2026, 4:02pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/15 "2026-03-13T16:02:58Z")
> [@Alex\_Rublev](#): > > I didnā€™t quite understand what the issue is with separating the DB and Lookups. I thought this was a valid approach: we keep all fields in one database, and from the second one we only pull in the fields that the user should see via lookups. Could you please clarify? Sure! We regularly recommend slicing a Database into two, a public one and a secret one, and connecting them with an automated one-to-one relation. For example, Projects DB + Project Financials DB or Podcasts DB + Podcast Rates DB. While this works in terms of pure access, user experience for a manager who has access to both Databases is dreadful. Instead of seeing all the Fields, both public and secret, together on a Project, they have to constantly navigate to the Project Financial to see the rest of the data. Lookups fail in this scenario because: - they arenā€™t editable; - they donā€™t respect the permissions of the source entity (everyone can see `Revenue` that you looked up from a ā€œprivateā€ DB via a one-to-one relation). If none of this is an issue for you, good šŸ™‚. Youā€™ll still be able to use Lookups/Formulas in a similar use case. ---
**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:** [March 13, 2026, 6:21pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/16 "2026-03-13T18:21:35Z")
Good, youā€™ve shared this. I did exactly this trick for my agency workspace where I have internal space (major one with all financials, hr, delivery, etc), contractor space, and client space. The last 2 ones have some shrunk dbs that are 1-1 connected to the core ones.