March 5, 2026 / 🙈 Hide Entity Views with rules, Specify which Entity View to open by default for a user, Validation rules on Create

:see_no_evil_monkey: Hide Entity Views based on rules

You can now hide specific Entity Views based on rules. This allows you to control which views are visible depending on logged user fields values or entity fields values. To enable Hide Entity View rules, click Views on entity view → … near view name → Set up rules.

In many setups, the same entity is used by different teams and across different workflow stages. Over time this leads to problems like: too many tabs on an entity, Views that are irrelevant for certain roles, Views that only make sense in specific workflow stages. With Hide View rules, you can automatically remove views when they are not relevant.

Some use cases:

  • Role-based visibility. Different teams may need different interfaces for the same entity.
  • Workflow stage-specific views. Some views only make sense at certain stages of work.
  • Different entity types in one database. When a database stores multiple types of work (for example Projects and Service Calls), some views may only apply to one type.

Let us know how it works and share any improvements ideas.

Hide Entity Views via Rules is Pro plan feature :money_bag:.

:speak_no_evil_monkey: Specify which Entity View to open by default for a user

Now you can use Logged User fields to setup rules for Default Entity View. It enables new use cases for default Entity View by:

  • User Role or Job Function. Show QA view by default for a user in QA role.
  • User Team. Show QA view by default if a user in QA team
  • User access, like Member vs. Observer.

To try how it works, Navigate to Entity View, click Views in the top right corner, select … and then Set up rules. Enable Open by default and specify User conditions.

:hear_no_evil_monkey: Validation rules on Create events

Until now, Validation Rules in Fibery worked only when entities were updated. This created gaps: entities could be created with invalid data and only later fail validation when edited. Now you can run Validation Rules at the moment an entity is created.

Notes:

  • Previous values are not available for Create triggers (since the entity did not exist before).
  • Rules can run on Create only, Update only, or both.

:red_exclamation_mark:Please use these rules with care. In some cases, users will only be able to create new entities via Forms, since there may be no good way to provide the values required by the validation rule outside of a Form View.

:butterfly: Improvements

  • Convert & merge / Rich Text / Back-references: previously, mentions in rich text and back-references were lost when converting an entity from one Database to another or merging one entity into another. Not anymore!
  • Architects: Now you can still add Views, setup Views and delete Views when Architect mode is off.
  • Activity Log:
    • Auto-linking events are now visible in Activity History for entity when you select All fields & formulas filter.
    • Degradation: is not and is none of filters removed from Trash bin and Activity Log to speed up these things.
  • Rich Text: Now when you copy markdown text (files with .markdown or .md file extension) from VS Code or other editors and paste it into Fibery, the text is formatted as needed
  • Whiteboard: Pencil now supports UI theme colors.
  • Beauty: New Warm theme is applied to reports and integration areas now.
  • Notifications: You can now control notifications for comment replies on entities. Turn reply notifications on or off per comment to stay informed about what matters most and reduce unnecessary noise.
  • Fibery MCP: Fibery MCP Support is added to Codex, n8n, Zed editor, Windsurf, Github Copilot in VS Code, Augment Code, Workato, Le Chat.

:shrimp: Fixed Bugs

  • Entity View:
    • Active Tab of Entity View is somehow jumping out of nowhere on page load
  • Filters:
    • Wrong value is displayed in pinned percent filter
    • Relative date select dropdown is hidden in date filter
    • New pinned filters buttons should be off by default
  • AI Agent:
    • Views: Agent is unable to filter by single-selects/states
    • Views: Agent allowed to group by date on axis
    • Views: Agent allows to create broken views when grouping multiple databases by enum field
  • Dashboard View: Unexpected resizing widgets on Dashboard after closing right panel
  • Gantt View: Filter values do not auto-apply to entities created on Gantt view
  • Relation Views: Issue with expanding in self-relation list (cards flickering and jumping)
  • UI:
    • Drop-down does not get expanded on click
    • Missing icon for the button in “Display as” menu
  • Home Page: ‘deleted field’ in filters for Home → My Work
  • Views: Snipped is not updated to empty value (description was completely removed)
  • Table View: Aggregation doesn’t recalculate when filter is applied
  • Documents / Rich Text: Language attribute is not serialized in Markdown
  • Search: Click on database select in search create new row does not open database select, but creates new entity

P.S. Your feedback helps us do mo things! :dog:

10 Likes

With the new Validation rules, Hide Entity Views based on rules, and Default Entity View per user features, things are getting seriously powerful.

We’re testing a full workflow here using Skills and Claude Code, but storing everything in Fibery: updating workflow progress, mixing human and AI reviews, and handling approvals end‑to‑end.

With all these new capabilities, working in Fibery is becoming a real pleasure.

6 Likes

I agree, this is a nice update.

2 Likes

Hey Guys! This is an awesome long-awaited update! :tada: Thank you!!

I’ll also pray for "Filters aren’t applied because they have missing ‘𝑥’ dynamic values" and the new Visibility Rules for buttons, etc. and better mobile app UX :slight_smile:

Fantastic!! Doesn’t this make required fields kind of useless?
I’m wondering if there’s a future where validation is per field, (auto create+update trigger), then if the validation is not empty, it shows the field everywhere on input, just like the “Name Using Formula” works. I think having it per field might make things a bit less flexible/repetitive (block 8 fields from changing if x if the case), so I’m not sure.

I’m not sure I see this as an improvement… Might confuse architects into thinking non-architects can also do it.

I hope validations rules will be reflected in UI and then this will be finally a solution to this maybe…

1 Like

No, but when we will add some UI to ask for missing fields, maybe. However, it is relatively hard and not planned for this year

1 Like

I’m so excited for these! One of the things I’ve been wanting for quite awhile! Thank you! :heart:

2 Likes

Yes! Thank you. This was a very fast turnaround on the issue. Event though the workaround was simple, this fix is amazing.

Like any ungrateful-sounding, but actually grateful :laughing: user: Now only if we could select and copy a part of the rich text as Markdown. Currently only the entire richtext gets copies when using copy as markdown, of course.

Haha I just consolidated a database on Sunday and realized that I lost all mentions after the fact. :sweat_smile:

This is amazing! Small bullet but huge possibilities.

1 Like

Another great one!! :sparkling_heart:

Just tried the “:see_no_evil_monkey: Hide Entity Views based on rules” based on a simple checkbox field, but the view is always displayed :thinking:

I noticed that a default empty “user condition” is always there when I open the configuration screen.

Even if I remove it, it always shows up.

1 Like

we will fix it

and we will check how it works with checkbox

Is this a correct behavior when I cannot change the operators?

For all checkbox fields, yes. Since “is” and “is not” is the same as checking true or false.

And user role is a special fibery field that is locked to only have that operator everywhere. Stumbled upon this yesterday as well. If you try other multi select fields it should have other possible operators.

Sounds like I’d have to re-invent the wheel, i.e. to create a custom User Role field to control visibility based on other conditions??

What kind of condition are you trying to set up and why is the ‘is any of’ predicate not enough for User Role?

Thank you for trying to help. It’s just a late evening and it’s time to have a break. I’ve checked again and looks like there’s no real issue. I’m sorry for fooling you guys.

Lots of awesome stuff to dig into on this release!

This isn’t working for me. The user groups relation isn’t showing as an option in the hide conditions. My user group database is a many-many with users, is that the reason?

1 Like

Please check whether Architect mode is OFF, otherwise we show all tabs