In September we did 4 releases with total 310 points (470 ā 280 ā 310 last 3 months).
Main product areas and how they will change with time in near future.
Permissions
Manage public sharing
We now provide an option to review and restrict public sharing for security-sensitive workspaces:
- 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: Share Entity to web via a link using access templates.
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 
:
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:
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:
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.
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.
-
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
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.
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
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.
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.
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.
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 
