🦭 Fibery Product Report: June 2025

[mdubakov]

As usual, here is our internal product report for June 2025 .

We’ve had 4 releases with 625 value points (440 → 400 → 625 last 3 months).

Main product areas and how they will change with time in near future.

Permissions

Capability-based Space permissions

We are (finally!) in the process of migrating to the new capability-based mechanism for Space access. At this point, nothing changes for the users, it’s purely an enabler for our next features. Okay, perhaps, Fibery will work slightly faster, especially for large workspaces, once we fully migrate.

Most internal services already support the new mechanism, you can see the progress based on the Dev Tasks here: Allow not to extend access from Space to its Databases.

The first two meaningful things after the migration would be:

• Allow to have Databases outside Spaces (in Default Space)
• Consolidate default access template names across Space, Database, and Entity levels

Access audit

We’ve introduced access audit on Space and Database levels so that architects can tell who has what final access and why:

• Show all Users who have access to a Space
• Show all Users who have access to a Database

Next step: Introduce access audit for Users and User Groups from the other side.

Adoption

Bad news first: it doesn’t look like those who have created but haven’t used custom access templates started to do so after Explain access templates:

It’s no better for workspaces created after our changes went live (Apr 24):

Maybe, people are just exploring custom access templates . We’ll need a proper qualitative research (aka a few interviews) to figure out what’s going on.

Good news: 40% of all collaborative workspaces now utilize User Groups and automatic access via People Field while over 30% share Databases, both numbers higher than expected:

Import

CSV

Over 200 workspaces have used CSV import in the last 30 days which shows the demand, and quite a few customers have complained about its deficiencies which shows the room for improvement. So we’ll continue working on the CSV import till we (and customers) are largely satisfied.

These were the two main things we delivered in June:

• Allow non-Admins to import data into existing Database
• Make switching from new to existing Field in integrations Field mapping discoverable

And here are the next major candidates:

• Import self-related entities via a single CSV file
• Update existing entities via CSV import
• Introduce optional Field settings in integrations and import

Additionally, it should be possible to import via the AI workspace builder.

Discoverability

A few small things:

• Suggest import or sync when adding a new Space
• Replace “Import data” with a nested “Import from…” menu
• Update headers for Database screens, including adding Import button.

We’ve postponed Skip authentication method choice if OAuth is available for the connector until we find someone with Vizydrop expertise to join the import team.

Notion

After we’ve learned how to fetch rich-text from Notion, the next step is to Sync Notion standalone Pages to Fibery Database.

Plus, make the connector stable.

Duplicates

Now architects can Automatically merge duplicates when enabling unique toggle:

The functionality is fully ready now, so we’ve started advertising it with the New badges.

If there is enough demand, we’ll introduce a way to find and merge duplicates without requiring future values to be unique.

Home page

We’ve released My Work widget and got immediate backlash in the community, since it is not flexible enough. This feedback came from mostly creators and it is unclear about its usage by mere mortals. We also did not promote it and did not make Home Page default (so far).

Then we had a conversation and decided to… implement Dashboard View. Plan is this:

1. Embed Views into Home Page with a dashboard-like layout
2. Basic Dashboard View (it will support Context Dashboard View as well as a result)
3. Admins want to configure Home Page for other users

So Kostya will spend July in these things. Behold!

Gantt View

Gantt View was released for Pro and Enterprise plans. It immediately became more popular than Map View and catching up with Thread View now .

We’ve made a serious mistake and based our Gantt View on board model, which lead to inability to show nested self-relations… Now we are re-doing Gantt View to support List model, fixing some bugs and polishing it. Should be done in ~2 weeks.

Then we will at least announce it in-product and see whether usage will be better.

AI

We’ve released the first version of AI Build mode as experimental, and some accounts started to use it. Overall, usage is not so great, but it is growing, so there is hope.

AI Agent got new tools, like semantic search and Fibery user guide, so now it is more capable.

Build mode has serious problems, since it can create databases with corrupted schema. We hope to fix these problems in the first week of July and release new getting started experience in July.

Other things we are working on:

• Add all views to Build mode (now it supports Table and Board only)
• Generate rules and buttons
• Make UI more pleasant with better context handling and artefacts

Whiteboard

In May, we released the first section updates and in June we kept improving them. You can now link and lock sections, and working with objects inside them is smoother. We also started improving how groups and selected objects behave. To better preserve data, we began updating the Undo history and will continue with Activity and Version History for whiteboards.

What we’re working on now and planning next:

• Groups improvements
• Use arrow keys to move multiple selected items
• Make “Undo/Redo” work well
• Whiteboard version history and activity
• Embed views into the whiteboard (reports, tables, etc)

P.S. Your feedback is welcome!

[Ryan_Dejaegher]

Dashboard view looks awesome! I know it’s possible to do this through columns and embedded views but this looks more intuitive and easier to layout.

[Mircea_Braescu]

@mdubakov

So Kostya will spend July in these things. Behold!

Looks awesome. The smoothest setup I’ve seen so far for setting up a Dashboard like layout was with PostHog. Yours looks like it might end up even better

[Ryan_Dejaegher]

@mdubakov this is probably on the radar but just in case, in this video
I talk about some bugs with the embedded whiteboard view

[Hendrik]

@mdubakov

Then we had a conversation and decided to… implement Dashboard View. Plan is this:

1. Embed Views into Home Page with a dashboard-like layout
2. Basic Dashboard View (it will support Context Dashboard View as well as a result)
3. Admins want to configure Home Page for other users

This looks amazing! Thank you!

Some questions:

• Will this be available on all plans?
• Will we be able to set up a Dashboard View for our clients (guests) that log in to a shared space? Would love to have a simple dashboard view where they can download the latest version of various document types (databases), see summary info etc. We would want to have one for different types of users which might have different data that is relevant to them.

---

@mdubakov

Embed views into the whiteboard (reports, tables, etc)

Awesome!
(Thank you!)

[interr0bangr]

@mdubakov

Then we had a conversation and decided to… implement Dashboard View. Plan is this:

1. Embed Views into Home Page with a dashboard-like layout
2. Basic Dashboard View (it will support Context Dashboard View as well as a result)
3. Admins want to configure Home Page for other users

Amazing!!! Love the mockup, it’s exactly what I was hoping for. Instead of a special “dashboard view”, is there reason why you wouldn’t just make the entire entity layout a flexible grid and then users can truly customize entities to their hearts content?

[mdubakov]

@Hendrik

Will this be available on all plans?

Yes, except Free

@Hendrik

Will we be able to set up a Dashboard View for our clients (guests) that log in to a shared space? Would love to have a simple dashboard view where they can download the latest version of various document types (databases), see summary info etc. We would want to have one for different types of users which might have different data that is relevant to them.

Dashboard View is just a View and nothing else. So it will work same way as Document with embedded views, for example.

[mdubakov]

@interr0bangr

is there reason why you wouldn’t just make the entire entity layout a flexible grid and then users can truly customize entities to their hearts content?

Fully custom entity view layout is MUCH harder to implement. Maybe someday we will do it, but not in near future

[mdubakov]

@Ryan_Dejaegher

I talk about some bugs with the embedded whiteboard view

Thank you! Views in whiteboard is a very early preview with many problems, we will fix them till the release

[RonMakesSystems]

@mdubakov

Fully custom entity view layout is MUCH harder to implement. Maybe someday we will do it, but not in near future

From what you’ve shared in the past it was due to having tricky “Defaults” for an dashboard layout of an entity. Maybe there’s other reasons not shared. But having a dashboard layout (along with single and double columns) would be really amazing. It would start blank, and would just another entity view layout. No need for defaults.

I’m just worried you are making the same mistake you made with documents in the past. Native documents vs. Documents database - #5 by mdubakov

Personally I’d prefer taking the time to do it right, than rushing to do it in a way that will be harder to fix later.

[Chr1sG]

@RonMakesSystems

I’m just worried you are making the same mistake you made with documents in the past. Native documents vs. Documents database - #5 by mdubakov

Personally I’d prefer taking the time to do it right, than rushing to do it in a way that will be harder to fix later.

Having ‘dashboard view’ as an option for sidebar views does not stop us from developing ‘dashboard layout’ as an option for entity view.
They support different use cases.

[jandrabek]

@mdubakov

Home page

We’ve released My Work widget and got immediate backlash in the community, since it is not flexible enough. This feedback came from mostly creators and it is unclear about its usage by mere mortals. We also did not promote it and did not make Home Page default (so far).

Then we had a conversation and decided to… implement Dashboard View. Plan is this:

1. Embed Views into Home Page with a dashboard-like layout
2. Basic Dashboard View (it will support Context Dashboard View as well as a result)
3. Admins want to configure Home Page for other users

So Kostya will spend July in these things. Behold!

So glad you decided to go this way. I don’t tend to criticize because everything you do has some background data and evidence based decision with logic typical to Fibery and even if you go wrong way you check usage, feedback and then make the right decision. For me Home tab was something I would never use. Dashboards are way to go. Thank you!

[mdubakov]

@jandrabek

So glad you decided to go this way. I don’t tend to criticize because everything you do has some background data and evidence based decision with logic typical to Fibery

We also do mistakes. A lot!

[jandrabek]

Oh my god! I love dashboard view and I’m surprised it came so fast. This is one of the best features ever I just love it so much I feel like crying

[Jan_Bilek]

We see the homepage as a key missing piece in Fibery. Our team often struggles to navigate the spaces that matter, and tthere’s no clear overview of what lives where. To work around this, we created a document called “ Home” to serve as our manual homepage with links to the most important views and documents. But it’s only partially useful since we can’t set it as the default for everyone.

[Matt_Blais]

@Jan_Bilek

But it’s only partially useful since we can’t set it as the default for everyone.

Allowing scripts/API to access and modify the left sidebar (for any/every user/group) would provide a general way to address this kind of issue.

But probably a better solution would be a UI for admins to define such customizations (for any/every user/group).

[Chr1sG]

@Jan_Bilek

Our team often struggles to navigate the spaces that matter, and tthere’s no clear overview of what lives where. To work around this, we created a document called “ Home” to serve as our manual homepage with links to the most important views and documents. But it’s only partially useful since we can’t set it as the default for everyone.

There is always a tension between companies where the admin wants to dictate what the non-admins see/do and other companies where non-admins want freedom to configure how their workspace looks/works.

This is what led to the splitting of the sidebar into ‘Workspace’ and ‘Personal’ (rigid vs freedom). If there’s nothing in a user’s Personal section, then they should always land on the top-most view in the Workspace section of the sidebar, meaning your “ Home” document could be the default landing for everyone if you put it at the top of the default space.

[Matt_Blais]

Perhaps a compromise would be to allow Admin to lock specific Workspace sidebar items, to ensure they always remain on top for certain users, regardless of user sidebar customization.

Ideally this would allow an admin to specify for which users/groups an item should be locked.

[Chr1sG]

@Matt_Blais

Perhaps a compromise would be to allow Admin to lock specific Workspace sidebar items, to ensure they always remain on top for certain users, regardless of user sidebar customization.

The ‘Workspace’ section is effectively locked by Admins. They have control over the default space. Non-admins cannot change the ordering of top-level items (but Creators can play around with ordering within spaces).