Technically, our progress is good and many things were done and released. Conceptually, there is a feeling that we are doing too much in too many directions and should concentrate/focus better on fewer things.
Granular Access. Decent progress → a major release is coming in May 
.- Simplify for architects. Quite a lot was done. →
- Simpler workspace toolkit. Quite a lot was done. →
Fibery Apps (so far just prototypes, will be a separate theme)
Make AI Agents happy. Quite average progress, this theme is not in our focus (we should have more people here).- Other. Slightly more distractions than in March
Granular Access
Done
We released two customer-facing features in the preparation for access to users:
- Share with users with a particular email domain that simplifies secure batch sharing by eliminating the need to introduce an auxiliary User Group DB.
- Allow users with trusted email domain(s) to join workspace that simplifies getting people into Fibery.
Adoption analytics are coming next month .
In progress
While both features 
are useful on their own, the main goal was to introduce the stepping stones to achieve this popular users visibility setting:
In case of a digital agency like fffff, everyone can see @fffff.com guys, and they can see everyone. Additionally, managers from each client company can see their colleagues.
Ideally, the email domain visibility should work for Guests as well, but we’ve faced a technical limitation to achieve that. Might come back to that eventually given enough feedback.
The goal for May is to release Configure who can see Users. This would immediately make Fibery a better platform for any org that collaborates closely with 3rd parties.
Next
We will do a few more smaller things to (hopefully) solve access to Users:
Core
- Allow users with the same email domain to see each other
- Configure who can manage Users
- Do not allow Users to see IDs of entities they don’t have access to: planned after access to Users.
Access templates
- Extend access to Users via access templates
- Automatically provide User Group members access to each other
Once we are done with Users, the next big thing is to rethink what everyone in the workspace can see in the age of AI: Do not allow Users to see IDs of entities they don’t have access to. This might also bring a significant performance boost.
In parallel, we’ll start Allow to hide Space data (entities) from Admins with Dmitry as the primary developer 
.
Simplify for architects →
Decent progress in this area in April, several nice problems were solved. We are stopping this theme in May so far. We may get back to it later if needed. For example, if we will find low hanging fruits here we may do them.
Done
- Duplicate action: copy many-to-many relations
- Show and edit related Entity Fields without a Lookup
- Automatically link entities: operators besides = (>, <, ≠, …)
- Search in context filters selects
- Fibery AI
- Ask/Build mode removal
- AI Integration Agent: Create, test and deploy integration for customer via chat
- Set AI context for Space
Next
- Redesign Database: Data header
Simpler workspaces toolkit →
We nailed the solution for Entity Templates, but postponed implementation till :viktar-zhuk: return from the vacation. Some nice features were done in this area, but for May we have nothing planned, except Custom Apps experiment. If we will find low hanging fruits here we may do them as well.
Done
- Filter and sort relation selectors in Form View
- Duplicate entity and deep-copy all 1-many relation tree
- When sorting, pick if empty values go on top or at the bottom
- Force users add entities via Forms
Custom Apps →
We’ve released Experimental: Create UI pages via chat and it got a lot of positive feedback. People started to experiment with it, liked the idea, but got some limitations, like small context window.
Now we’re re-creating the same idea with the new technological stack that looks more scalable and promising. We hope to get this feature on edge soon Experiment: Custom Apps and with some polishing release as a new prototype for the customer to check.
I think this is a very promising direction, aligned with “Code is becoming easy to write, how it affects Fibery future?” vision.
Custom Apps deserves its own initiative it seems, since they can bring Fibery to the new niches and new markets, so from the next update most likely this will replace Simpler workspace toolkit theme.
Make AI Agents happy
Some progress is there. Some MCP improvements, and new API guides is the most significant improvement. Finally, our API guides are easily accessible by AI Agents and we will continue to improving them.
We thought that Semantic Search will be part of this theme, but abandoned the idea so far. In general, only Max and partially Sergey worked on this theme and it is definitely not enough.
Done
- Add an action to fetch an entity/view by URL
- Embed View (iFrame View)
- Migrate API Guides from User Guide to a separate resource
Next
Rich text should be ready for agents. First two things we will focus on are:
- Suggestion mode for documents
- Update small part of rich text via MCP tool or API
MCP Server improvements. MCP usage is spreading. Stats for recent weeks. MCP unique workspace: 375 (connected MCP server). We are going to improve it more and there is some hope to make it permissions-aware:
- MCP Server reliability
- MCP and AI agent tool: Add comment
- AI Agent should access Files content (+ attach file into chat)
- Open Agent: Build for Architects (not only admins) + make agent permissions-aware
- Create & Update Whiteboard View with AI
Interaction with external agents is the next step, and we will start with the most basic thing we can have - just call AI Agent via webhook, so Eugene will implement Send web request action.
- Send web request (post to webhook) action in automations.
Growth
Done
After 42 iterations, we released Adjust main (aka Database) palette based on theme:
Fibery looks much better in the warm theme now. Thanks to everyone who contributed their feedback!
In progress
Final changes to themes:
- Architect can select unusable colors for Databases and Spaces
- Full Database Badge and New item button may have unusable user-defined colors (too low contrast)
Meanwhile, Reports are the last place to beautify before graduating the warm theme from beta:
- Adjust reports (vizydrop) palettes based on theme
- Bugs in Apply custom theme in vizydrop reports (& import from CSV)
Once Reports are ready, we’ll promote the warm theme among existing users and call it a day.
Other
Search improvements →
We decided to not invest into better semantic search for now. Effort is huge, value is very questionable. Stats for recent weeks for databases that were added to semantic index: keyword: 2,810 (78.5%), vector: 110 (3.1%), keyword_and_vector: 658 (18.4%). Pavel will try to improve keyword search, add people filter, and then switch to something else.
- Give more priority to recently modified things in search
- Relax title matching to OR (any word matches)
Next
- Filter by Created by and other People fields
Rich Text improvements →
Here we fixed a lot of bugs and implemented long requested feature Text and Background Color. Final improvement in rich text theme is also highly requested unification of lists Bullet and checklist improvements. In May we will not spend more time on rich text improvements (well, only relevant to “Make AI Happy” theme)
Whiteboard
Add the ArchiMate shape setwas done and now we are finalizing Add additional shape and icon libraries.
Maybe the last important feature for Whiteboard is Whiteboard Templates. Maybe we will take it.
Other other
Done
- Webhooks UI
- Files theme finalized with Sort files
- Some integrations improvements, including Integromat: upload and attach files
- Unexpected hotkeys foundation improvement Migrate from react-hotkeys dependency
- Mobile
- Show the TOC on mobile devices in compact mode
- Update Tabs on Mobile
- Update Share panel on Mobile
Next
- We will implement Fibery steps in Slack Workflow Builder for customer X.
- Handle Large Datasets in Tables
- Customize load limit (aka page size) for embedded View (Table, List)
- Have own columns for nested items and do not merge columns to include more fields without changing width for customer Y
P.S. Sorry for the delays, report for May will be ready with a better timing. As you see, this report for April aged like a milk in some areas with little progress already 