March 20, 2025 / Manage users like any other Database, Improved drag and drop in the left sidebar, many fixed bugs

This release once again contains many quality of life improvements and many fixed bugs :sun_behind_cloud:.

Manage users like any other Database

When it comes to managing users in a workspace, we are moving away from a custom and hard-coded approach in favor of using the Fibery building blocks you are already familiar with.

This update includes three changes in this direction:

  1. User DB appears in the sidebar for Admins in “builder” mode (show DBs with an icon-button on top), so you can manage fields and automations in a familiar manner.
  2. The fake People “Space” becomes a regular Folder, so you are free to delete, rename, or move it as you see fit.
  3. User role becomes available as a column in Table View, so you don’t have to visit settings every time you want to upgrade someone from an Observer to a Member.

Eventually, we will deprecate the current Users settings and make it possible to manage users just like any DB, including inviting and deleting as well as custom actions like deactivating and changing email.

Improved Drag and Drop in the left sidebar

Drag and drop in the left sidebar was re-worked. Now menu items don’t jump, drop zones are clearly indicated and everything works smoother and sharper.

Fibery MCP Server

Fibery MCP Server is here.

You can now chat with your Fibery workspace through Claude or any other MCP-supporting LLM. Current tools enable LLM to check schema, query databases, create and update entities.

Here is an example how you can fetch information about competitor and update relevant entity in Fibery with a single phrase. Check it out!

:butterfly: Improvements

  • Automations: Added support for collections in IF branches within Automation Formulas. You can now set a field with a formula that returns a collection in an IF branch. For example, you can set a People field based on conditional logic.
  • Multiple Entity Views: When creating a field from a specific Entity View, it’s now visible only in that Entity View by default and hidden from others. Note that fields added directly from the Database are still added to all Entity Views.
  • Whiteboard: Comments now support reactions, allowing users to provide quick feedback.
  • To eliminate confusion, we’ve reversed the visualization of monthly limits in workspace status from 10/100 left to 90/100 used and added color coding.

:shrimp: Fixed Bugs

20+ bugs were fixed in this release.

Timeline View

  • Focus gets lost in ‘Filter lane’ field under certain conditions
  • Entities display and save incorrectly when daylight saving time is involved
  • Content flashes briefly when scrolling left
  • Week delimiters appear in incorrect positions
  • Quarter headers display inaccurately

Sidebar

  • Selected state not applied to views from default space when opened via direct link
  • Non-admin users can incorrectly move Smart Folders from Space to Folders in Default Space
  • Firefox: Difficulty making collapsed sidebar reappear
  • Inconsistent space ordering behavior: new spaces from scratch added at beginning, template-based spaces added at end
  • Missing progress indicator when deleting Spaces

Entity View

  • Poor formatting for checkboxes with long names
  • Copy button missing for Progress bar unit

Rich Text

  • Layout breaks in ‘Create highlight’ pop-up — button appears outside pop-up boundaries
  • Text formatting popover hidden when selecting long text segments

Whiteboard

  • When changing color for different lines, only the color should update, currently, all styles (e.g., thickness) are inherited
  • Copying thread link creates infinite scroll-to-anchor loop

Miscellaneous

  • Duplicate Groups appearing in Entity sharing popup after Group relation deletion
  • Reports: Unable to set context filters for all databases when multiple are selected
  • Field Creator: Primitive fields created via long-running jobs (e.g., checkbox for large integrations) incorrectly marked as public
  • Focus not automatically set to first required field for “name generated via formula” entities
  • “Fibery user” displays instead of actual username in document history when entity added via form with required fields
  • List view: Missing ‘Add after’ option in right-click context menu when no grouping is set
12 Likes

This is one of those “makes perfect sense” features.

This will make the AI geeks in our team happy.

1 Like

Both these things are very much appreciated!

Ooh interesting. Never thought of setting it up like this. It means for less automations to maintain. Wondering if its possible to clear a collection using a formula. If true, set it to something, if false, clear the relation. Or does this still need to be two automations?

Thanks!

Unfortunately that’s not possible for now.
We need some special function that will correspond to empty result.
Like coda.io for example has List() function in their formulas.
We will think about it, thanks for the feedback.

2 Likes

Because automations support the concept of a database ‘entity query’ it is in fact possible to clear a collection field by making an entity query that returns an empty set, e.g.

If([Step 1 Task].State.Name = 'Done', Users.Filter(true = false), [Step 1 Task].Assignees)

As smart as that is, it doesn’t seem to be working for me… :frowning: :
Failed to execute Action “Update”: Cannot parse value for “Office/Share to project portal” field in “Office/Version” database. Cause: Invalid uuid .

Formula:
If(
[Step 1 Version].[Send for Client Revision] = true,
[Step 1 Version].[Project Portal],
[Project Portals].Filter(true = false)
)

Are you updating a collection field or a to-one relation?

to-one. That may be the problem?

Yep. In that case, you’ll need [Project Portals].Filter(true = false).Sort().First()

(this was possible to do before today’s release BTW)

Ah perfect! That works thanks! One less automation to maintain.

User role becomes available as a column in Table View, so you don’t have to visit settings every time you want to upgrade someone from an Observer to a Member.

THIS is SO great. LOVE IT, along with all the other improvements from this release.

I’m super interested in this whole MCP thing too – Anyone have any good primers on how to get this setup? (Pretend like I’m 5 years old)

2 Likes

Nice! I like this!

I think I remember seeing some talk about other “system” databases, like docs in the future. Will these have a special space/folder/section in the left sidebar to be unified?

Yay! I’m so happy with this improvement! So many times I had struggled with trying to drop items either into a folder or just below it.

2 Likes

This is a decent guide For Claude Desktop Users - Model Context Protocol

Some particularly nice releases. Improved drag and drop is always good too!

I remain impressed and excited by your weekly releases. Thursday is now a highlight every week as I see which issues you’ve tackled. Looking at your current Roadmap, I’m particularly excited for the Gantt View and the Unique Values in fields (but there’s lots of good stuff on it of course!). From your Unsolved Problems post, I’m also really excited for Polymorphic relations, as that’ll be helpful in making things a bit more end-user friendly in places. But I know there’s tonnes of other improvements coming that I’ll love as well.

Good work, Fibery team! :clap:

1 Like

Are there plans to introduce automations for Users DB? I recall this was tried before with scripting but was not possible. Or allow Fibery forms to be the signup. Where one could create a new username and password in the form and it signs them up.

This way we could set up custom sign up form, or allow non-admins to invite users through automation.

But you can do it if press this database icon

Ah I think I didn’t explain it right. I mean automate “Create entity” action for the Users DB. So that any member can create a “Profile” entity and an automation will run to create that user and invite them to the workspace. Or at the end of the hiring process, it creates and invites a user.

This action is not on the radar so far. It looks interesting, but use cases are quite limited imho. It can be quite easy to add too many people by mistake, etc, automations are quite dangerous here.