September 24, 2026 / 🍟 Better tables in Rich text, See where a field is used before you delete it

Changelog
1

Our designers have started coding! Beware! :french_fries:

Better tables in Rich text

Working with tables in documents just got a lot smoother:

  • Drag to reorder rows and columns. Hover over the left or top edge of a table to reveal a grip. Hovering it highlights the whole row or column. Click to select it and open the menu, or drag to move it anywhere in the table.
  • Right-click for everything. Right-click any cell to select it and open a menu with all table actions.
  • Colorful cell highlights. The single grey “Mark cell” option is gone. You can now pick any color from the text highlight palette and apply it to a cell, row, or column.
  • Clear contents. Empty the selected cells in one click, without deleting rows or columns.

See where a field is used before you delete it

Deleting a field used to be risky. You deleted it, found out what broke, brought the field back, fixed everything, and deleted it again.

Now, when you delete a field, Fibery first shows you where it’s used: formulas, lookups, automations, and reports, even in other databases. Click any item to open it and fix it first.

If you just want to take a look where a field is used, click Check usages action on any field and explore the list:

delete-field
delete-field1920×1235 306 KB

LIMITATIONS:

  • If a field is used in Automation Scripts or Markdown template, it is not included into this list.
  • In the next releases we will expand this list and add all views, validation rules, access templates and maybe even custom apps.

New fields are not added to all entity views

If a database has several Entity Views, new fields no longer added into all of them. Create a field right from an Entity View, and it shows up only there. Create it anywhere else (Database screen, other Views, integrations, API), and it stays hidden until you add it in Manage Fields and columns. No more cleaning up views one by one after new field addition!

Choose pages width in documents and entities

Documents and entity views now have three width modes, so they look good on any screen.

  • Narrow is best for reading. Lines are shorter and text is easier to follow.
  • Medium works well for most screens and everyday work.
  • Wide gives you as much space as possible. Handy for big tables or large monitors.
    Try them out and pick the one that suits you.

Show document history changes in entity activity and activity log

Now rich text fields updates inside any entity are visible in the changes history. So far only the fact of the update is visible and you have to click to see additional details about what was changed.

image
image1920×1158 324 KB

:dashing_away: Performance

Faster updates across Views. We’ve made a sizeable cut in the work Fibery does when entities change, so busy views should feel noticeably more responsive. The improvements are especially useful in large workspaces where teammates, automations, and Integrations keep things moving. We’ve also trimmed some processing work during initial loading.

We have ~1.5 people (with many parallel agents) working on performance now, so regular updates are expected.

:butterfly: Improvements

  • Automations: Notify Users action now sends a notification even if the user doesn’t (yet) have access to the corresponding entity — useful when you assign them (= give access) with another action in the same automation.
  • Fibery AI:
    • Fibery AI agent can now search the web, and fetch content from public pages in LLM-friendly format
    • Latest models added to Fibery AI, including Opus 5.5, GPT 6 Sol, GPT 6 Luna

:shrimp: Fixed Bugs

  • UI:
    • Left sidebar gets hidden while floating menu is shown
    • Database setting panels did not inherit new panel styles
    • Entity View: Manage Fields popover focuses Hide all instead of field search
    • Views: ‘Group by’ and columns settings can not be cleared — clicking on ‘Clear’ button just expands list
    • ‘Story’ Database fails to be found via Search in the left menu sidebar
    • Different icons for the same trigger in Rule and Validation rule
    • List of fields for auto linking is too narrow and cut when positioned down
  • Fibery MCP Server:
    • Views: AI Action fails on “field: null” in orderBy
    • Reports: AI action fails if database is not in schema
    • MCP responds with incorrect whiteboard’s URL
  • Whiteboard:
    • Sometimes text gets disappeared on switching b/w headings
    • ⌘/Ctrl + option+ Up/Down keys should not lead to nodes creation
    • Z-index issue with menu for filter group
    • Empty field units are not displayed on the card when the “hide when empty” setting is turned off
    • “Canvas:IDpool is overflowed” error on duplicating whiteboard
    • Lack of arrow between linked images
  • Relations: Different search results in relation list with self-relation when show/hide units
  • History & Audit Log: Comments cannot be loaded in history
  • Documents / Rich Text: An image is duplicated in rich text when a user drags the image itself instead of using the drag handle
  • Smart Folders & Context empire: Filters are failed to be saved for Smart folders
  • Undelete (restore) / Undo: Clicking Undo on an inaccessible entity’s history record shows no UI error
  • Custom Apps: Public link to custom app works incorrect in text editor

P.S. We keep making Fibery better for you every day (well, except most weekends) :yellow_heart:

14 Likes
Hide fields and views tab on entity for non architects
September 17, 2026 / New Fibery AI Agent, Whiteboards and AI, Space templates with files and images, OAuth Applications
Flag invalid relations/lookups
[DONE] Content container too wide? Narrow the width of the container of content pages
[DONE] Show Field References
[FIXED] New Fields Automatically Pollute Multiple Entity Views
[DONE] Do not show new fields in existing entity views
3

All welcome & appreciated! Really, really glad for the New fields are not added to all entity views & See where a field is used before you delete it!

2 Likes
4

Thank you! I was sweating away yesterday trying to work with the tables so this is great timing :folded_hands:

3 Likes
5

this is a brilliant little quality of life for humans improvement thank you

5 Likes
6

Really good week.

Love the “see where a field is used” and “new fields aren’t added to views” updates.

Is the plan to add Automation Scripts and Markdown template to the field usage check at some point in the future? Maybe when either of those are saved, you could analyze the text for any reference to a field? To me, scripts is essential because they’re often the ones that typically have the most critical and complex jobs that can really break things if you’re not careful.

2 Likes
7

Very cool.

Long waiting !! Thanks

Finally !! Thanks

What about adding an “Auto” option to make it adapt automatically based on the screen/page size ?

Great too

Very nice update, thanks !

2 Likes
8

Thanks a lot for all the table improvements! Very happy to see those! And seeing where fields are used before deleting is great too! Happy to see all these refinements continuing.

1 Like
9

Fantastic! Love this.

As said by others here: Finally!

This is lovely. Changing rich text now also changes the “Last modified” of the entity? I’m testing this and I can’t seem to get it to work though. Sent you a video on intercom.

This gets me super excited!!

This as well :))

It is felt! Thank you!

10

Also, just noticed: when changing field types, fibery actually deletes and recreated a new field. (One-to-many → many-to-many, for example). This breaks the field usage in places just like “Delete” does, but it does not get the same popup saying things will break.

Tbh, there isn’t much you can do, since you need convert it anyway, and then fix. In which case, you’d need this: Notify/show broken formulas in rules BEFORE they fail

The main case is Field Updates and “Add to collection” automations. Since it does not throw any error until runtime.

1 Like
11

It looks like everyone is back from holiday. This is an incredible release!
So many Fibery feature improvements and most impactful for me: better table editing :partying_face:
The every day wins are in the details and it’s nice to see some polish come to so many.

Thanks Fibery team!

4 Likes
12

I’m loving this update so much! Very nice quality of life improvements for various aspects of our workflow.

Does this mean that people can now receive notifications when a rich text field is updated!? :eyes:

1 Like
13

Next week hopefully.

2 Likes
14

Lots of really great things in this release!

I haven’t used tables a lot because they were a bit clunky, but this looks like it’ll solve the issues I had.

Huge! I’ve been eagerly awaiting this one since you mentioned you were working on it.

Finally! Such a small feature, but when you have many views it will save a lot of time!

Nice to see cohesiveness.

This is really big for me. I’ve noticed quite a few long loading times or straight-up errors when loading over the past several months. (Caveat: I’ve been actively importing lots of data and building. I’ve also reported when it’s been particularly bad, and any issues on your end that were quickly resolved.)

I’m trying to sell Fibery as a solution for a ~30-person business where the majority aren’t techie and want things to just work, while also needing quite a complex solution. They’re very interested in the functionally I’ve showed them, but I know if things are slow/not working, I’ll get a lot of complaints, so it’s very encouraging to see incoming updates in this area!

2 Likes
15

See where a field is used before you delete it

Thanks a lot for this one! Other improvements are great as well though.

2 Likes
16

Wow, thank you. So many improvements, among them the following that really help:

17

I think I’m gonna cry (in a good way!) so many QOL improvements that will help me

  • Better tables in rich text
      • Thank you, so much better!
      • Can you also add an alignment selection? For example, number columns need to be right aligned
      • The AI Agent can create tables in a Rich text (which now look much better) but they also expand horizontally far beyond the edge which then has scroll (which is not good). There is no way to set “fit columns” or fixed column width or something like that to try and contain the table. This happens a lot when producing reports which are heavy with tables/graphics
  • See where a field is used before you delete it
    • I’ve broken so many reports doing this in the past
    • Can Agents access this via MCP or API? It would help if they understand impact of making change before they do it
  • New fields are not added to all entity views
    • Love it
  • Performance
    • Agents should be so good at this. Hopefully this also improves the sync speeds I noticed pauses during batched updates. My guess was it’s waiting to reclac all formulas and relation heavy dbs before requesting next batch?

Keep up the great work guys!

1 Like
18

This has already come in so handy, and I came here to say "it would be nice if you could see where a field is used for Views - and you’re already working on it :+1:

19

Yes we can! October 1, 2026 / đŸ”„ Custom Apps as Entity Views, Suggestion mode for rich text

1 Like