# đŸŒ» Fibery Product Report: July 2025 **URL:** \ **Category:** News & Announcements\ **Created:** [August 6, 2025, 8:44am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362 "2025-08-06T08:44:15Z")\ **Posts on this page:** 12\ **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:** [August 6, 2025, 8:44am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/1 "2025-08-06T08:44:15Z")
In July we wrapped up Home Page, Dashboard and Gantt View themes. Good progress with AI Agent. Some progress with Permissions, Whiteboard and Import. A little progress with Mobile. We’ve made 5 releases with **470** points of total value ( **400** → **625** → **470** last 3 months). ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/55888299d1894f9cf376d152092fd9c67e2f4a61.png) Main product areas and how they will change with time in near future. ![Screenshot 2025-08-06 at 11.30.55 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1d3728a873986d9d106e9e8d8f6cf629e1945ca3.jpeg) You can watch July updates webinar [![](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/ecff41a64862436a47ee90ea6a8277d453b77780.jpeg "Fibery product updates — July 2025") ](https://www.youtube.com/watch?v=wJc2In4gh4U) ## Permissions (via Anton) 🐌 July has been a largely uneventful month, since a lot of work happened under the hood, Andrew supported features in other areas (Home, import, etc.), and Dima had a vacation. ### New Space permissions The old model has been switched off in the edge environment and is about to be switched off in production đŸ€ž. This would signify the successful transition to the new model and unlock the long-awaited user-facing Features: - _Consolidate default access template names across Space, Database, and Entity levels_ - _Allow not to extend access from Space to its Entities_ - _Allow to have Databases outside Spaces (in Default Space)_ Meanwhile, we’ve decided not to wait and fixed a small but impactful problem even before we have proper permissions for the default Space: _Allow everyone (including Guests) to see Smart Folders in default Space_. ### Hiding data from Admins Previously, we disregarded this problem as not solvable, but it seems like we’ve found a decent way on how to _Allow to hide Space data (entities) from Admins_ without breaking the permission model or introducing a ton of complexity. We will require each Space to have at least one Creator with access to data, but it won’t have to be an Admin. The whole thing becomes possible thanks to decoupling access to Space and its entities. There is a risk we will stumble upon an unfixable vulnerability and will have to abandon the idea, but it looks promising now. ### Access audit for Users and Groups Soon, it will be possible to get the full answer the question “what does this person or team has access to?”: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2de35c84b37aa461a5f9b32fb58864f15d1c0541.png) `Manage access` page for Users and Groups will include both direct and indirect access. For example, you’ll see that someone has read access to all Clients because their Team has been granted `Viewer` access to the corresponding Space. ### Access changes in Activity Log Access is a sensitive topic. When someone loses or gains access when they shouldn’t, it triggers an investigation, sometimes sprinkled with anxiety. Since there are no records in the activity log, customers ask customer support for help who, in turn, ask Andrew and/or Aleksey that have to switch context. In the ensuing temporary information vacuum, everyone becomes a suspect, including us. After a few awkward incidents, we’ve decided to reprioritize _Track access changes (aka permissions) in history_ higher: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4dbb56c4020a7ac2b66589a7f2471d6887f43473.png) ### Scaling automatic Entity sharing Now as many collaborative workspaces use automatic access to entities via People Fields as do manual entity sharing â˜ș: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/28be5e1f9a84cbccca1bcae47e08db83f671b070.jpeg) I was optimistic about the functionality, but even I didn’t dare to predict that. ## Import (via Anton) ### CSV We’ve made a few improvements to save our users from juggling data before import: - _Import self-related entities via a single CSV file_ - _Support simpler Date Range format in import_ We’ve also revamped the guide: [Import from CSV](https://the.fibery.io/@public/User_Guide/Guide/Import-from-CSV-67). The next big thing is _Update existing entities or skip duplicates via CSV import_: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9e51d255c8ca69c22c2f6127fa65139593eb54d5.png) This Feature was made possible by _Introduce create-or-update (upsert) entity command to API_ that we are looking to reuse in more places later, automations and forms being the primary candidates. CSV is still the most popular import by far with almost 2 million entities across 163 workspaces over the last 30 days: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/07ad1e56ece0d12713f968e0227764c42cf3cb12.png) ### Simplification Integrations used to be among the nerdiest and least accessible bits of Fibery, so we’ve addressed this: - _Simplify Import UI_ - _Denerdify integration authentication_ ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/abbe1a9f2da6ccd3ddf472b2f2dac2f44c7ae8cd.png) ### Stability Integrations and import used to be quite unstable in certain conditions which made for terrible UX, so we’ve addressed that: - _Do not delete running imports during sync service restart_ - _Relation data is (partially) empty after import_ - _Timeout on import Notion standalone pages_ ### Other connectors Thanks to Max, we quickly reacted to a customer’s complaint and added _Linear: Issues and Projects support dependencies_. _Confluence integration & import_ looks like the next big thing to help people move from their existing tools. ## Home page & Dashboard (via Michael) Dashboard view was released. We did all the features we wanted and are closing this theme so far. Home page got a few widget updates (notably, it was converted to Dashboard mechanism and users can insert views now). We put on hold a separate Workspace Home page that admins can customize and want to hear more feedback. It seems like Dashboards can solve this problem as well, so we don’t want to do it right now. The last feature remaining is to make Home Page default (and add a choice for a user to set). Dashboard has ~50 WAU now, but it was fully released only in the end of July, so maybe it will be better soon. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/060962f82b5b281c6cadb35f37b57bd51ff2cdff.png) In general, this theme is done and Kostas is moving to Mobile. ## Gantt View (via Michael) We’ve fixed the major problem and now Gantt View can support unlimited self-relation hierarchy. We also implemented several quality of life features, so Gantt View now should be quite good. Gantt View has ~40 WAU now and no growth at all
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2099eac46965cc261e05a0d9911c130cd736a241.png) This theme is also closed and Misha + Pavel will spend some time (~August) on Views and UI polishing. ## AI (via Michael) In July we improved Build mode and AI Agent can create almost all Views now (except Whiteboards and Reports). A lot of bugs were fixed and we moved Build mode out of experimental. AI Agent also answers Fibery-related questions now and public user guide transitioned from old bots mechanism to new Agent mechanism. We are working on _Create an Automation (Rule or Button) with AI_ and better results formatting (with links to exact views, fields, etc). Our next steps with the Agent - _Finalise automations creation_ - _Create Whiteboard View_ - _(maybe) Create Reports_ - _New AI-based getting started_ Max is also working on _Remote MCP for Fibery_ to enable Claude partnership and more use cases. AI Agent adoption is slowly growing. Builder (or Architect) mode is also growing, which is good. With the new getting started we will have a serious test of its performance, so we will see. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/81ab96a884bd6e0748abe28e36472c6820820e36.png) ## Whiteboard (via Alex) In July we released improvements for object groups _Whiteboard: Groups improvements_ and fixed some major issues in the Undo mechanism _Whiteboard: make “Undo/Redo” work well._ After that we switched to _Whiteboard activity_ and _Whiteboard version history_ - two of the most important areas in the whiteboard from the user’s perspective. Victor has started developing Activity, Vadim is working on improving the connection algorithm and will switch to _Embed views into the whiteboard (reports, tables, etc)_ ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7a5cfccb6d1688994b254d51d1c7715825b91018.png) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2e61b87f014a4f6a0fdcc15ba74d37f96a8c4e02.png) ## Mobile (via Alex) In July, there was some progress on the mobile app Mobile , I was mainly focused on designing the navigation and core screens. We’ve got a small group of beta testers. Dima set up the build service for iOS and Android. We will start with a navigation update _Navigation toolbar_ for the client: adding a navigation bar for quick access to Home, Search, and Agent, and beginning to update components to follow mobile patterns. ![Screenshot 2025-08-06 at 11.40.31 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/fd23161e33f2e26e9f2ff028216a1e4335fba672.jpeg) Next steps: - Update core components - Update main navigation - Update view/entity toolbar - Rich-text toolbar and comments - Notifications for iOS/Android - Settings ## Some random metrics - We have 700+ paid customers now - Our MRR growth is ~2x during the last 12 months - We have ~1300 new leads every month and ~50 new paid customers - Our development speed is still great, even in Summer we have decent weekly releases P.S That’s all for July, post your comments, ideas and emotions below. Thank you 🙇. ---
**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:** [August 6, 2025, 8:44am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/2 "2025-08-06T08:44:22Z")
---
**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\ **Post date:** [August 6, 2025, 9:43am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/3 "2025-08-06T09:43:32Z")
Thanks for the detailed update and all the improvements big and small, under the hood and on the surface. The improved permissions sounds like a key stone going forward! Also happy to see that the whiteboard and mobile get love still! 🙂 Still need to try the dashboard, but I can say that each space I always added a basic home (README) page explaining the purpose and listing the owner. Whenever I added new pages, this page got moved down as new pages got inserted on top. Thanks and happy summer! ---
**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:** [August 6, 2025, 10:24am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/4 "2025-08-06T10:24:46Z")
> [@mdubakov](#): > > Hiding data from Admins Surprised and happy to see this! This would unlock possibilities for us. We aren’t able to bring in some data currently as there are things that I (as admin) should not see. > [@mdubakov](#): > > Access changes in Activity Log This would be helpful! We’ve had one instance where this feature would have been good to have. > [@mdubakov](#): > > Mobile Excited to see more progress on this! Thank you all! ---
**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:** [August 6, 2025, 1:37pm UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/5 "2025-08-06T13:37:38Z")
This is super exciting! > ### Hiding data from Admins > > Previously, we disregarded this problem as not solvable, but it seems like we’ve found a decent way on how to _Allow to hide Space data (entities) from Admins_ without breaking the permission model or introducing a ton of complexity. > > We will require each Space to have at least one Creator with access to data, but it won’t have to be an Admin. The whole thing becomes possible thanks to decoupling access to Space and its entities. This is huge!! It saves us from having to bring on a neutral IT admin, as the current admin in a cooperative is also one of the members and so could be seen as having a conflict of interest – this will add trust to the system and significantly reduce our staffing burden. Very big upgrade and increase overall to data privacy. Thank you!! > Now as many collaborative workspaces use automatic access to entities via People Fields as do manual entity sharing â˜ș: It’s an excellent feature that no other tool in this class really touches: it’s the #1 reason we moved from Notion. > Dashboard has ~50 WAU now, but it was fully released only in the end of July, so maybe it will be better soon. Dashboard is actually a big upgrade for us, but we have to plan out the bandwidth of using the dashboard views. The one limit we see is not being able to insert ‘headers’ that help you visually make sense of groups of widgets in a busy dashboard. Our team tends to like very busy dashboards, but it becomes a bit problematic when you can’t add headers. Of course, we can workaround this and plan to start switching to dashboards, but it’s a 6 month timeline for us. I imagine this is true of some of the really neat upgrades: people have to think about them for a while, then tinker with them, and then finally start deploying them as they understand how to fit them into their workflow more. > We’ve fixed the major problem and now Gantt View can support unlimited self-relation hierarchy. We also implemented several quality of life features, so Gantt View now should be quite good. > > Gantt View has ~40 WAU now and no growth at all
 Gantt is a super big deal for us. It was one of the ‘wishes’ we had that we had to sacrifice when we came to Fibery. For us at least the lag in adoption is the same as explained above – we have to make some internal changes to fully use the Gantt chart, which is probably a 6-month project for us due to our own internal time constraints – so it looks like we’re not adopting even though we’re actively building out to get ready for heavily using Gantt views. > In July we improved Build mode and AI Agent can create almost all Views now (except Whiteboards and Reports). A lot of bugs were fixed and we moved Build mode out of experimental. > > AI Agent also answers Fibery-related questions now and public user guide transitioned from old bots mechanism to new Agent mechanism. > > We are working on _Create an Automation (Rule or Button) with AI_ and better results formatting (with links to exact views, fields, etc). > > Our next steps with the Agent > > - _Finalise automations creation_ > - _Create Whiteboard View_ > - _(maybe) Create Reports_ > - _New AI-based getting started_ > > Max is also working on _Remote MCP for Fibery_ to enable Claude partnership and more use cases. This is one of Fibery’s best features (other than permissions) – we tend to keep it limited so we don’t run out of credits, but this is a very much appreciated feature improvement! > - Our MRR growth is ~2x during the last 12 months > - We have ~1300 new leads every month and ~50 new paid customers > - Our development speed is still great, even in Summer we have decent weekly releases Yay! ---
**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\ **Post date:** [August 6, 2025, 2:47pm UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/6 "2025-08-06T14:47:13Z")
> Thanks to Max, we quickly reacted to a customer’s complaint and added _Linear: Issues and Projects support dependencies_ . Thanks Max!!! ---
**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:** [August 7, 2025, 2:28am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/7 "2025-08-07T02:28:56Z")
> [@mdubakov](#): > > Max is also working on _Remote MCP for Fibery_ to enable Claude partnership and more use cases. This is awesome! 👏 ---
**Author:** ![Hendrik](https://avatars.discourse-cdn.com/v4/letter/h/839c29/32.png) [@Hendrik](https://community.fibery.io/u/Hendrik)\ **Post date:** [August 7, 2025, 7:39am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/8 "2025-08-07T07:39:37Z")
> [@mdubakov](#): > > Soon, it will be possible to get the full answer the question “what does this person or team has access to?” That’s great, thank you! > [@mdubakov](#): > > Update view/entity toolbar Great. I hope this includes the ability to hide the toolbar on views, particularly in docs (will post separately about this need) ---
**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:** [August 12, 2025, 9:18pm UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/9 "2025-08-12T21:18:41Z")
Can we get mobile for testing at our own risk? 😃 ---
**Author:** ![alex](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex/32/52_2.png) [@alex](https://community.fibery.io/u/alex)\ **Post date:** [August 13, 2025, 9:19am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/10 "2025-08-13T09:19:49Z")
We’re currently working on a test build, and as soon as it’s ready for release, I’ll send invites to everyone who wanted to participate in the testing 👌 ---
**Author:** ![cover](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cover/32/11891_2.png) [@cover](https://community.fibery.io/u/cover)\ **Post date:** [August 13, 2025, 9:21am UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/11 "2025-08-13T09:21:11Z")
Please include myself also! Or where to subscribe? 🙂 ---
**Author:** ![alex](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex/32/52_2.png) [@alex](https://community.fibery.io/u/alex)\ **Post date:** [August 13, 2025, 1:08pm UTC](https://community.fibery.io/t/fibery-product-report-july-2025/9362/12 "2025-08-13T13:08:15Z")
Sign up here to join the beta release 👌 [Fibery Mobile beta](https://the.fibery.io/@public/forms/EXFG696u)