April 30, 2026 / Force users add entities via Forms, Allow users with @your.domain to join workspace, new API guides

[mdubakov]

Several quality of life improvements today.

Allow users with @ your.domain to join workspace

You’ve decided to adopt Fibery but can’t be bothered with inviting people? Now you can allow anyone with your org’s domain to join the workspace without an explicit invitation.

Go to Settings → Security, set trusted domains, and enable the corresponding toggle. You can also select if people join as Members (can have any access but take a paid seat) or Observers (can only read and comment but are free) by default.

For now, this only works when users sign in with Google/Microsoft, not email + password. Let us know if it’s a bummer for you.

Force users to add entities via Forms

Sometimes when users create new entities and click +New in a views or other places, they only see the name field (or required fields). They skip other important fields, leaving entities half-filled.

Now you can always show some form to users. Navigate to form and enable Require filling in this Form when creating.

Note that this works per-database, so in most database you can have simplified entities creation flow, while for important databases you can enforce forms usage.

NOTE: Force users add entities via Forms is a Pro plan feature

As a nice addition, all forms created for a database are visible in Forms section inside the database.

Adaptive palettes

Can you spot the differences :

Previously, when you switched from neutral to warm theme (go and try it in Settings → Preferences if you haven’t), the colors of Spaces, Databases, selects, and callouts remained exactly the same. Cold as ice. Foreign to the warm theme.

Now palettes adapt to the chosen theme. Blue remains blue, but the exact HEX changes ever so slightly to feel balanced within the surroundings. We bet you’ll barely notice the change, but your subconscious should appreciate the harmony.

API Guides migrated to a new home

Fibery API documentation has a new home now: developers.fibery.com.

From now on, that’s the place to go for everything API-related. We’ll remove the API docs from the User Guide soon.

In fact, the main motivation was your feedback in this community. You were right that the Fibery User Guide is not the best place to read API documentation.

We’ve also improved API documentation itself and made sure that LLMs can utilize the API reasonably well after reading these docs.

The next step we are working on is a new Schema API (working with Schema, Databases, and Fields). We aim to produce a straightforward API so that anyone can set up their workspace with code.

We know that the Fibery API is not an easy beast to tame. While we’re focused on this area, we are eager to listen to your feedback. What parts annoy you the most? What do you miss? What tasks do you want to solve but currently can’t?

Improvements

• Mobile: Share panel improved
• Integrations:
  • It’s no longer possible to set sync from date as a future date in Email connector and this prevents some problems
  • Now it’s easy to delete accounts from accounts list
• SAML SSO. Specify the default role for JIT provisioning, choose between Member and Observer.
• MCP Server. Improved tools description, and you should see less mistakes. We’ve discovered that anthropic truncates any tool description to 2048 characters in Claude Cowork and Claude Code (and our query tool description was 9k characters). We minified query tool description to 1.7k.

Fixed Bugs

• Forms:
  • Sometimes relation filter does not get applied in the new Forms
  • After filter is open, first toggle has tooltip visible
• Mobile: Opening the action menu is broken in the mobile client
• Files: “Download all files” should be hidden in public spaces as it leads to “Unauthorized” error
• Integration: “Undefined” in account name if there name is empty
• Dashboard View: Favourited smart folder blocks access to dashboard sub-widgets
• Table View: broken layout for a long entity name used in grouping
• Sort: Empty value sorting doesn’t work in columns/rows on views
• Documents / Rich Text:
  • List item loses its bullet marker (and sometimes its indent) when editing adjacent items
  • Fixed a bug when pasting a large markdown document with base64 images
  • Existing list item loses its bullet marker when a new bullet is inserted above it
• Getting started: Missing email/name in welcome to Fibery email in some cases
• History & Audit Log: Filter by schema change does not work correctly in Trash bin
• MCP Server: get_documents_content tool reduces the document at 10k chars

[timothy]

“Force users add entities via Forms” - yay! Thank you!
Also love the MCP upgrades!

[helloitse]

@mdubakov

Fibery API documentation has a new home now: developers.fibery.com.

Big win for the devs today! Thank you all so much!
Any chance we’ll be able to have user submissions in the near future?

[Sev]

Just amazing!

I started copying sections for quoting here; but then I stopped when I realised that I basically copied almost everything.

Almost everything in this update seems addressed to us directly! Well done. Thank you.

[mdubakov]

@helloitse

Any chance we’ll be able to have user submissions in the near future?

What do you mean? Create API docs?

[Alex_Rublev]

Much appreciated — all the improvements are exactly what I needed!