# Fibery Product Report: October 2024 **URL:** \ **Category:** News & Announcements\ **Created:** [November 4, 2024, 1:01pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727 "2024-11-04T13:01:13Z")\ **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:** [November 4, 2024, 1:01pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/1 "2024-11-04T13:01:13Z")
We’ve made five releases in October (overall, weekly schedule is very consistent now). Total Highlights Score: **405** (for comparison, it was **770** in [September](https://community.fibery.io/t/fibery-product-report-september-2024/7572)). ![60238dd7-d5ee-4838-a70a-a5432a0b95cd](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/14af1e563d60fdcc7f927d7299392fbef4b7edfa.png) Main areas we focused on in October: - Permissions - New pricing and payment system (out of scope of this report) - Space Setup - Search - Navigation ## Permissions ### Done We’ve released the first version of [Introduce Guests limited to per-Entity access](https://the.fibery.io/@public/User_Guide/Guide/Share-Entity-233/anchor=Sharing-with-an-external-collaborator--dc815b1f-148b-4e63-9bcb-f585bcc988db). It took exactly one month since the kickstart which is great for a Feature involving so many people and services. Now we’ll see if Guests in their current form are enough to solve the majority of external collaboration use cases. ### Next We have leftovers from the Features we’ve just released that we’d like to cover: - Finish the Guests Feature: fix non-critical Bugs left and finish the small sub-Features. - **Convert Assignments into regular People Fields** to erase confusion about why some Fields behave differently than others. - **Improve Guests user experience** : in particular, how sidebar navigation works for them. The next big thing is **Share Entity with Group** : Andrew has already started his part, and we’ll do a proper kickstart this week. **Share Database with Group** would follow. ### Adoption Almost as many workspaces use automatic access for assignees as those who share manually. 50+ workspaces have granted DB access: ![6a7cbddd-2c49-4f70-9d0c-21d86e62397a](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b956577bb777440c19204e524c4a13d0401d5fe8.png) ## Simplicity & Usability ### Creator usability improvements We’ve mostly focused on problems related to Fibery workspace setup and streamlining the creator user experience. Major change was new Space Setup design. It caused some problems, but it seems we found good solutions to all of them, so in November we will polish Space Setup and make it shine. **Done** - Space Setup 2.0 - Convert relation Field: to-many → to-one - People Field - Settings Page: Integrations - Move Folders between Spaces **Next** - Oleg decided to not move forward with AI for automation rules, but give AI Q&A a second chance (he will try to change the approach, so we will see how it goes.) - New Space Setup: Fields screen - Other Space Setup improvements around navigation and relation screen. ![42a948e6-67c4-46cb-86c2-e1831b68222d](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7ff96dbdf0e096bdfef6a083457b30a7e9330bf2.png) ### Rich text improvements Sergey decided to make rich text better. First, he improved rich text loading time by 10-30%. Now the goal is to remove jumps in rich text fields and documents and preload all mentions: **Avoid jumps when loading mentions in Fibery Documents**. It should make rich text experience much better. ### Adding and updating data We’ve decided to fix all major problems related to adding and updating data in Fibery. In October we’ve released Quick Add. Other major features will include Required Fields and Batch Updates. I hope we will be able to complete them by the end of the year. **Done** - Create anything from sidebar / quick add **Next** - Required Fields - Improve Entity creation when formula is used for name (or some fields are required) - Batch edit Entities from Views other than Table ### Sidebar Suddenly we decided to fix Fibery Sidebar. First, we made it completely collapsible and added Cmd + \ hotkey, this is just a start. Main idea is to introduce custom Sections, so it will be possible to move Spaces to these Sections. Usual users will NOT be able to re-order sections in the left sidebar, but just hide them. As a result, it will be easier to enforce a proper structure of the sidebar for creators, but end users will have slightly less control on the order. To compensate that, we will improve Favorites section: it will be possible to create folders in Favories and also add Spaces to Favorites. This any curious and savvy user will be able to fine-tune Favorites and just hide everything else. Less curious users may be happy with the default sidebar configured by creator. **Done** - Completely collapse left sidebar **Next** - Quick Filter Views in all Spaces - Collapse all spaces with a single click - Folders in Favorites - Add Spaces to Favorites - Sections (Special, Custom, Smart) and make Spaces order in the left menu predictable for all users ![Paper.Product_dev..48](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/75e02da0c6e9a92a66672b53a1a9ec670b720834.png) ### Search We did some improvements for search and tried to merge semantic and keyword search results. It affected performance and now search feels slower for 2+ keywords. We also played with re-ranking algorithm and results were better, but it added ~0.5 seconds to results display time, and so far we disabled it. - Search in basic text/email/phone Fields - Semantic Search Results mixed with keyword search results **Next (maybe in December)** We are making a pause in Search improvements to think, but possible next search features are: - Search exact match using quotes - Semantic search setup simplification - Find duplicates for target (or any?) entity ## Email/CRM Theme This theme should be completed on October (at least MVP). We did two small features, and are working on a major feature that will allow to sync several email accounts into a single Email database. We also will implement some integration with data augmentation service, so it will be able to enrich Leads/Accounts with some information automatically. - Email Integration: Cleanup email body - Add Email URL Field to Email integration **Next** - Integration with some data enrichment system - Multiple accounts for the same integration ![40f7f3c9-be52-4c53-ab51-504c75da5f77](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2dae23d4a2c11a06d156c3288326e9aebe1e2e59.jpeg) ## Whiteboard It appeared that bringing ProseMirror into Whiteboard is a very challenging task. We already spent 6 weeks on it and it is not done yet (but close). In the meantime, some small additions were made here and there to the Whiteboard. ### Done - New shapes: Pill, Quote and Attention - Holding Shift modifier key while moving an item on the board, should keep the item sticky to the X or Y axis - Whiteboard: Copying text and style to apply formatting to objects - When a whiteboard is opened and the user’s viewport is empty, automatically adjust the view to fit the screen if there is any content on the whiteboard - Preserve selected database in search popup for current Whiteboard ### Next We are still fixing basic things to make Whiteboard good. It is already much better and people noticed that. - Whiteboard: Text Editor floating Menu - Adding and displaying external text links on the whiteboard - Comments in Whiteboard (maybe in December) P.S. Your questions and ideas are welcome, as always. With 🧡, Fibery Team. ---
**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 4, 2024, 1:01pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/2 "2024-11-04T13:01:26Z")
---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [November 4, 2024, 2:14pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/3 "2024-11-04T14:14:43Z")
Looking forward to many of these improvements. > [@mdubakov](#): > > We did some improvements for search and tried to merge semantic and keyword search results. It affected performance and now search feels slower for 2+ keywords. We also played with re-ranking algorithm and results were better, but it added ~0.5 seconds to results display time, and so far we disabled it. Definitely noticed the reduction in speed. One thought that might help is ability to search by just one or more “Spaces” and select multiple “Databases”. This way, it doesn’t search the entire workspace every time but you still have the flexibility of searching more than one database. ---
**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:** [November 4, 2024, 5:58pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/4 "2024-11-04T17:58:15Z")
Great report! The consistent enhancements to our daily workflows across Fibery’s recent product releases leave no doubt that we chose the optimal solution for our company. This conviction is further strengthened by the reality that the majority of planned future improvements directly align with the suggestions and ideas our team had previously proposed as valuable enhancements. When the Fibery product roadmap so closely mirrors our own assessed needs and recommendations, it unequivocally demonstrates the development team possesses a comprehensive understanding of our requirements and is resolutely committed to addressing them. Thank you to the entire Fibery team for your responsiveness and user-centric approach. We greatly appreciate the continued effort to evolve the product in lock-step with our evolving needs. ---
**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 4, 2024, 6:15pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/5 "2024-11-04T18:15:05Z")
> [@Illusory](#): > > One thought that might help is ability to search by just one or more “Spaces” and select multiple “Databases”. This way, it doesn’t search the entire workspace every time but you still have the flexibility of searching more than one database. This is not a problem, major problem is general slowness of AI search. Now we wait till both searches return results and mix them. ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [November 4, 2024, 6:57pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/6 "2024-11-04T18:57:44Z")
Possible idea: Split search results into two “panes” horizontally (one above the other). Each one is titled, e.g. “Fast Search” or “Basic Search” and “AI Enhanced” or whatever (you have better ideas, I’m sure, hah). Then show top 5 results from “traditional” search on top, immediately (as soon as they are ready), and populate the AI search below it as soon as those results are ready (show some indicator that it is loading in the meantime, e.g. spinner or whatever). Don’t mix them. At the bottom of each Top 5 you have “show more” or “expand” that will expand that specific set of results into the current infinite scrolling list (and at the bottom it still shows the “AI Enhanced” bar below it, clicking that will expand those results to top 5 bringing it back to default state maybe). Perhaps also figure out some way to optionally enable “mixed” results, e.g. a default-collapsed “Combined Search” section at the top that you can click to expand, and hopefully by the time you click it the AI results are ready. 😄 I guess maybe there are complications from interaction with keyboard shortcuts or other issues, but maybe it’s the seed of an idea. Btw Claude is great for quick mockups! 60 seconds to create the prompt (based on my description here), provide a screenshot of current search box UI, a little directed refinement, and within 2-3 minutes boom: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/ad02dd61246984080715f9db31e686bceea9a2bf.png) Bottom line for me is that the recent “enhancements” to date have not been an overall improvement. I am hopeful of the “best of both worlds” because I didn’t use AI search very often before, partly because it was a whole different “mode” that I had to enable. If I could see the top 5 results of each fairly quickly I think that would be quite helpful. The main benefit of AI search is to bring up a relevant result much quicker, higher in the sort order (when it works, for particular searches), and I can usually evaluate that with the top 5 or so results. If the AI’s top 5 is not clearly closer to what I want, the traditional search results are more likely to be worth scrolling through beyond top 5 because the AI’s results tend to digress _further_ the more you scroll (in my experience). Plus the AI results are loading while I am evaluating the relevance of the top 5 faster traditional search results. Similar principle as loading a skeleton of the UI before you are able to load data, makes it feel faster, and in this case genuinely _is_ in a functional and not just psychological way. ---
**Author:** ![Nevil\_Hulspas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nevil_hulspas/32/4703_2.png) [@Nevil\_Hulspas](https://community.fibery.io/u/Nevil_Hulspas)\ **Post date:** [November 4, 2024, 9:09pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/7 "2024-11-04T21:09:31Z")
> [@mdubakov](#): > > **Next** > > - Required Fields Oh yeahh 🕶 ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [November 4, 2024, 10:22pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/8 "2024-11-04T22:22:34Z")
> [@Oshyan](#): > > Possible idea: Split search results into two “panes” horizontally (one above the other). I was actually thinking this! ![CleanShot 2024-11-04 at 17.20.00](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/58b3f5998a3f007558211b2db51342a6b87f14d9.jpeg) Or maybe split horizontally. ![CleanShot 2024-11-04 at 17.21.42](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7bcb81c2a22f3dee418e9e7e5d9ac3837ce65449.png) ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [November 4, 2024, 10:34pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/9 "2024-11-04T22:34:29Z")
I would have suggested horizontal except I am biased from being on 4k all the time and I’m not sure the majority’s screens would ideally support the width. But if so, great! Side-by-side would be better for UI/UX IMO. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [November 4, 2024, 10:37pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/10 "2024-11-04T22:37:51Z")
I’d opt for “responsive” 😅 ---
**Author:** ![robyn\_bieber](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robyn_bieber/32/6183_2.png) [@robyn\_bieber](https://community.fibery.io/u/robyn_bieber)\ **Post date:** [November 5, 2024, 1:17am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/11 "2024-11-05T01:17:16Z")
CSS please. 🥹 ---
**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 5, 2024, 6:26am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/12 "2024-11-05T06:26:11Z")
> [@Oshyan](#): > > I would have suggested horizontal except I am biased from being on 4k all the time and I’m not sure the majority’s screens would ideally support the width. But if so, great! Side-by-side would be better for UI/UX IMO. A lot of our people are remote and mobile, working on laptops, so a vertical split would be better for most of our team, whereas a side-by-side view would create too much clutter and would make it too difficult to see all the data (too much left-to-right scrolling). I imagine the horizontal split would only work on larger screens if the search pane was the only pane open. If search is opened in a second pane, then I imagine a vertical split providing a better UX. ---
**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 5, 2024, 7:07am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/13 "2024-11-05T07:07:24Z")
> [@Oshyan](#): > > Possible idea: Split search results into two “panes” horizontally (one above the other). Two areas for results is not an ideal solution, since there will be two scrolls, no way to use keyboard and other usability problems. We will not go there. ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [November 5, 2024, 7:26am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/14 "2024-11-05T07:26:18Z")
Fair and reasonable. But still… think outside the box 😁 ---
**Author:** ![Giuse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/giuse/32/8487_2.png) [@Giuse](https://community.fibery.io/u/Giuse)\ **Post date:** [November 5, 2024, 7:29am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/15 "2024-11-05T07:29:08Z")
About requires fields, I’d suggest to target a wider approach where each fields support 2 formulas: one to drive show/hide state and the other to drive required/optional state That would deeply enhance flexibility, in particular to complex scenarios. Thanks a lot for these monthly updates! ---
**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 5, 2024, 7:31am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/16 "2024-11-05T07:31:40Z")
> [@Giuse](#): > > About requires fields, I’d suggest to target a wider approach where each fields support 2 formulas: one to drive show/hide state and the other to drive required/optional state > That would deeply enhance flexibility, in particular to complex scenarios. Can you expand this idea with some use cases? For required field there will be just a checkbox in settings “Required” ---
**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 5, 2024, 7:32am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/17 "2024-11-05T07:32:05Z")
> [@Oshyan](#): > > Fair and reasonable. But still… think outside the box 😁 Oh we always love ideas! ---
**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 5, 2024, 7:46am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/18 "2024-11-05T07:46:23Z")
> [@mdubakov](#): > > **Improve Guests user experience** : in particular, how sidebar navigation works for them. Yeah. Share item in menu is not good enough. I found workaround where I create smart sections - Tasks, Projects, Clients and Guest see only items that are shared with them in these sections. Problem is that they see all the smart sections even when empty for them. ---
**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 5, 2024, 7:56am UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/19 "2024-11-05T07:56:57Z")
> [@jandrabek](#): > > I found workaround where I create smart sections - Tasks, Projects, Clients and Guest see only items that are shared with them in these sections. Problem is that they see all the smart sections even when empty for them. This is exactly what we will fix, improve and simplify ---
**Author:** ![Giuse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/giuse/32/8487_2.png) [@Giuse](https://community.fibery.io/u/Giuse)\ **Post date:** [November 5, 2024, 3:03pm UTC](https://community.fibery.io/t/fibery-product-report-october-2024/7727/20 "2024-11-05T15:03:17Z")
Yes: in many cases fields can be dependent on values of other fields, both in terms of being required or not and meaningful or not. For example: an entity can be a task that can be repetitive or not, a field “is recurring?” drive the appearance of period of recurrency, that is not meaningful if the task is not repeatitive so it must be hidden, while it is meanigful and required if the task is repeatitive. [Next page](https://community.fibery.io/t/fibery-product-report-october-2024/7727.md?page=2)