# April 30, 2026 / Force users add entities via Forms, Allow users with @your.domain to join workspace, new API guides **URL:** \ **Category:** Changelog\ **Created:** [April 30, 2026, 1:55pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787 "2026-04-30T13:55:14Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 30, 2026, 1:55pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/1 "2026-04-30T13:55:15Z")
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. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f803bc13812a88961fc4fb1e254fa1a5bb57d49a.jpeg) 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`. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/902c9b14cae5e5e4cc84f95cec180fc7e7981e0b.jpeg) 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 🧐: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/70119b66fb003d4f3655b8e634dcad73934124dd.jpeg) 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**](https://developers.fibery.com). ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/dcd0fa9a063b6736c03b2a6894d109d6299ce58a.jpeg) 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](https://code.claude.com/docs/en/mcp#for-mcp-server-authors) 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 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 30, 2026, 1:55pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/2 "2026-04-30T13:55:21Z")
---
**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\ **Post date:** [April 30, 2026, 2:23pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/3 "2026-04-30T14:23:32Z")
“Force users add entities via Forms” - yay! Thank you! Also love the MCP upgrades! ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [April 30, 2026, 3:17pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/4 "2026-04-30T15:17:12Z")
> [@mdubakov](#): > > Fibery API documentation has a new home now: [**developers.fibery.com**](https://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? ---
**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\ **Post date:** [April 30, 2026, 3:28pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/5 "2026-04-30T15:28:04Z")
💯 👏 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. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 30, 2026, 3:57pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/6 "2026-04-30T15:57:53Z")
> [@helloitse](#): > > Any chance we’ll be able to have user submissions in the near future? What do you mean? Create API docs? ---
**Author:** ![Alex\_Rublev](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex_rublev/32/10881_2.png) [@Alex\_Rublev](https://community.fibery.io/u/Alex_Rublev)\ **Post date:** [April 30, 2026, 6:46pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/7 "2026-04-30T18:46:37Z")
Much appreciated — all the improvements are exactly what I needed! ❤ ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [May 1, 2026, 12:08pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/8 "2026-05-01T12:08:17Z")
> [@mdubakov](#): > > Allow users with @ your.domain to join workspace I WAS WAITING FOR THAT !! THANKS !! 🤩🤩🤩🤩🤩 ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [May 1, 2026, 12:22pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/9 "2026-05-01T12:22:59Z")
I hope we will be able to create User accounts by API soon 🤓 _(From Pro plan please)_ ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [May 2, 2026, 10:00am UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/10 "2026-05-02T10:00:34Z")
> [@Jonathan1](#): > > I hope we will be able to create User accounts by API soon 🤓 Well, you can already create users via the [SCIM endpoint](https://the.fibery.io/@public/User_Guide/Guide/SAML-SSO-49/anchor=SCIM-endpoint--28f6310b-b95c-4885-a3ee-064f7f0a08a2) if you’re using SSO. I assume this won’t fly in your case, right? By the way, what should the user role of those users be in your scenario? ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [May 5, 2026, 1:45pm UTC](https://community.fibery.io/t/april-30-2026-force-users-add-entities-via-forms-allow-users-with-your-domain-to-join-workspace-new-api-guides/10787/11 "2026-05-05T13:45:03Z")
> [@antoniokov](#): > > By the way, what should the user role of those users be in your scenario? Thanks for the input and yes, we have an SSO. I will touch it back with my colleagues.