In October we did 5 releases 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.
Main product areas and how they will change with time in near future.
Permissions
Public sharing via access templates
The new entity public sharing using access templates is live 
:
We also have a pair of new shiny guides:
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): 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
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:
- Introduce custom access templates for Databases access. No template management UI for now, API endpoints only.
- Configure access to Users
- Add create capability to access templates
- 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!
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)
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
and Gallery View
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…
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.
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! 
