# September 18, 2025 / ⚔️ Specify which Entity View to open based on some field value **URL:** \ **Category:** Changelog\ **Created:** [September 18, 2025, 1:54pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616 "2025-09-18T13:54:59Z")\ **Posts on this page:** 20\ **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:** [September 18, 2025, 1:54pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/1 "2025-09-18T13:54:59Z")
While we’re working on Fibery Mobile 🎅, new permissions core upgrade 🐌 and re-writing our AI Agent almost from scratch 🥲, we still can deliver some useful things to our adored users. ## ⚔ Specify which Entity View to open based on some field value You can now set rules that open a specific, pre-configured Entity View based on a field’s value — like **Project Type** , **Feature State** , **Task relation** , and more. It’s a simple way to show the most relevant information to users when they open an entity from any place. 💰 This is a [Pro plan](https://fibery.io/pricing) feature Here are few use cases that you may find useful: 1. **Different project types.** Open a tailored view for Integration, Service, or Maintenance projects—each with its own fields and relations. 2. **Tasks that change context.** Show different information when a task belongs to different projects or teams. 3. **Accounts by type.** Show a focused set of fields for Client, Vendor, or Partner accounts. 4. **QA focus during testing.** Auto-open a “QA” Entity View when a Feature moves to In Testing to show bugs and test notes on top. ## Layout enhancements We’ve cleaned up the app layout so it feels lighter and easier to use: - Sidebar resize handle is now on the left side of the leftmost panel = no more extra border clutter. - Panels shadows are more prominent, giving them better contrast. - Light theme got a touch brighter in background and the AI pane. - Loader background now exactly matches your color theme. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/ec012709a650f6fc10fde3eea972baacb674baa7.png) ## Sync People Fields in integrations From now on, no matter if you invite users from your other tools to Fibery, you can sync People Fields properly: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7e50c14af64664ed9716c67fb1bcea908b447d66.png) It’s already working for ClickUp with Notion coming soon. You can also import/sync People in your own [custom integration](https://the.fibery.io/@public/User_Guide/Guide/Create-Custom-Integrations-83). We’ll update the docs soon — meanwhile, don’t hesitate to reach out for help. Do you miss this in other integration? Please let us know by sharing your use case. ## 🦋 Improvements - **Permissions:** capabilities that Observers (aka read-only users) cannot receive are shown as such in access audit. - **Activity log:** inaccessible entities are displayed as `Untitled` instead of `Private `. - **ClickUp integration:** users are added to Fibery as Observers by default, although you can sync them as a separate Database or skip altogether. ## 🦐 Fixed Bugs - **Whiteboard:** - Black color instead of grey is shown in pen color palette in dark mode - Arrow is not drawn properly when images linked until user refreshes whiteboard - Error when click on actions button (…) on whiteboard in public Space - When selecting an arrow type in the menu all connectors switch to one type - The border is misplaced on changing size of text on line - JS error on removing section name - **Audit History:** - Integration Databases always miss createEntity capability in access audit - Inaccessible entities are displayed as `Untitled` instead of `Private ` - **Flexible Domain:** It’s impossible to merge parent entities if relation field is marked as required from the child side - **AI Agent** (Build mode): - Format value is missed for created Number fields - Agent populates defaultValue in form with dynamic date which is not allowed - **CSV import:** CSV import issue if file has column named ‘id’ and contained duplicated data P.S. Share your emotions or feedback, we always happy to hear from 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:** [September 18, 2025, 1:55pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/2 "2025-09-18T13:55:06Z")
---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [September 18, 2025, 2:28pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/3 "2025-09-18T14:28:24Z")
> [@mdubakov](#): > > Specify which Entity View to open based on some field value Absolute game changer. This will make work in our multi tenant setup way more intuitive. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [September 18, 2025, 2:41pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/4 "2025-09-18T14:41:38Z")
Lovely stuff! Curious what’s to come from the new AI Agent. Some thoughts as always :)) > [@mdubakov](#): > > ## ⚔ Specify which Entity View to open based on some field value This is cool, but I was really hoping there would be user context here. If assignee = me, open one view, if its not me, open another. This was the main use case I saw. I also notice there’s no option for filtering on collections, ie: contains any of, contains none of. And there’s also no “is empty”, or “contains”. Ideally the filters here are the same as filters configurable in views (incl. filter groups). Not sure if this is on the roadmap for improvement now, some time in the future, or not at all. > [@mdubakov](#): > > - Sidebar resize handle is now on the left side of the leftmost panel = no more extra border clutter. I like this style. ![Screenshot 2025-09-18 at 15.29.16](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/c40c093bddf5fbb09abcd59bcec2b64a0ed2492f.png) But it looks a bit off when there is horizontal scroll in the main container. The nav feels like it should be behind the panels, yet it actually goes on top of the panels. Even in things like table or board view , the nav feels like its going in front when scrolling horizontally, when in this new style it feels like its behind. And the line above Help and Support and below Workspace/Personal goes all the way to the edge. Which maybe should stop a bit before the edge maybe? Not sure. ![Screenshot 2025-09-18 at 15.40.54](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8e798a09cfe918bd760963823ab9daa5f1e7dd57.png) Excited for whats to come! ---
**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:** [September 18, 2025, 2:42pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/5 "2025-09-18T14:42:04Z")
Completed agreed - love this feature!! This is one of this ‘gift’ surprises you didn’t know you wanted and are completely excited about once you get it! ---
**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:** [September 18, 2025, 2:44pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/6 "2025-09-18T14:44:39Z")
> [@RonMakesSystems](#): > > This is cool, but I was really hoping there would be user context here. If assignee = me, open one view, if its not me, open another. This was the main use case I saw. I also notice there’s no option for filtering on collections, ie: contains any of, contains none of. And there’s also no “is empty”, or “contains”. Ideally the filters here are the same as filters configurable in views (incl. filter groups). Not sure if this is on the roadmap for improvement now, some time in the future, or not at all. Interestingly, we had exactly 0 requests to add assigned = me, most use cases were around exact field value. We are not going to complicate things here so far, but we will collect feedback and decide if it will be necessary. ---
**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:** [September 18, 2025, 3:01pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/7 "2025-09-18T15:01:44Z")
I second more contexts – I’ve wished before that I could set a view by role (e.g., of the person opening it) – and maybe ESPECIALLY by where I opened it from. For example, if I opened it from the project relation field, then open it in X view, but if I open it through the budget relation, then open it in Y view (but this sounds more like a link issue then a rule). I wonder if you could specific in a View which entity view to open? For example, in a “Budgets” view I could specific that the entity opens in the “Money” tab, and in the “Projects” view I could specific it opens in the “Project Status” tab? That would be absolutely amazing, and enable very user-friendly UI. Of course, if it’s not specified, then it would just default to the first tab or whatever. ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [September 18, 2025, 3:02pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/8 "2025-09-18T15:02:50Z")
Team or Job function is another use case that would be relevant to us Like, if a “deliverable” was being viewed by someone on the “QA team”, they would have different buttons or fields shown than things than people on the “production team”. ---
**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:** [September 18, 2025, 3:04pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/9 "2025-09-18T15:04:12Z")
Indeed we have requests to open views based on user role. It is relatively tricky to implement, so we are just collecting feedback so far ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [September 18, 2025, 3:31pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/10 "2025-09-18T15:31:22Z")
Hey hey! Hooray. 🙂 > Specify which Entity View to open based on some field value 😍 Am I the only one here who gets so excited to see Fibery’s updates every Thursday, like it’s a release of a new iPhone back in 2008? ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 18, 2025, 3:32pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/11 "2025-09-18T15:32:16Z")
Normally I’m a cheerleader for releases, so apologies in advance. 😄 I guess this change to Entity Views must be why I woke up this morning to have **all** my entity views now with collapsed Properties sidebar. 😠 And on my other (work) account they are even defaulted to 1-column mode. I think I recall in the past this was something to do with me not having changed the defaults and so the defaults got updated and overrode what I had or something. I wish that wouldn’t happen, but if it has to, well, still **strong** disagree with defaulting to 1 column and/or collapse properties sidebar state! Is there some way I can bulk fix this across all DBs? Yes it only has to be done once per-DB (I think/hope), but this is the 2nd time something like this has happened and it’s frustrating to have to go through again. Also… > [@mdubakov](#): > > - **Activity log:** inaccessible entities are displayed as `Untitled` instead of `Private `. This strikes me as a bad way to handle this. “Untitled” _is_ an actual state or even a name in some cases (like if a name defaults to “untitled”). Why not just say “inaccessible”, “no permissions”, “na”, or something else that’s actually accurate? The entity is _not_ untitled in this case, is it? If it’s not literally untitled this is not the way to handle it IMHO. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 18, 2025, 3:39pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/12 "2025-09-18T15:39:40Z")
> [@Oshyan](#): > > > [@mdubakov](#): > > > > - **Activity log:** inaccessible entities are displayed as `Untitled` instead of `Private `. > > This strikes me as a bad way to handle this. “Untitled” _is_ an actual state or even a name in some cases (like if a name defaults to “untitled”). Why not just say “inaccessible”, “no permissions”, “na”, or something else that’s actually accurate? The entity is _not_ untitled in this case, is it? If it’s not literally untitled this is not the way to handle it IMHO. Actually, we are fixing a bug where “inaccessible entities are displayed as `Untitled` instead of `Private `” but I can see how the announcement makes it read like the reverse. ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 18, 2025, 3:52pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/13 "2025-09-18T15:52:00Z")
Hah, oh right. I forgot how the fixes are often stated. So it seems we are in agreement about how to handle it. 😁 ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 18, 2025, 4:00pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/14 "2025-09-18T16:00:23Z")
> [@Oshyan](#): > > I woke up this morning to have **all** my entity views now with collapsed Properties sidebar. It seems we made a mistake, and you were unlucky enough to be affected. We’re rolling a hotfix, and sending our apologies 🙇 ---
**Author:** ![Pavel](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/pavel/32/3903_2.png) [@Pavel](https://community.fibery.io/u/Pavel)\ **Post date:** [September 18, 2025, 4:31pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/15 "2025-09-18T16:31:18Z")
> [@Oshyan](#): > > I woke up this morning to have **all** my entity views now with collapsed Properties sidebar. 😠 Fix is deployed, apologies for the inconvenience 🙏 ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 18, 2025, 5:23pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/16 "2025-09-18T17:23:02Z")
Yay, thank you for the quick response! You guys are the best. 🙂 I do see some of them fixed, though at least one DB was still in collapse state. Perhaps because I toggled it and it remembered my change, I don’t know. But hopefully all the others are back to the proper default, 2-pane, uncollapsed state. 😅 ---
**Author:** ![ccollins](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@ccollins](https://community.fibery.io/u/ccollins)\ **Post date:** [September 18, 2025, 5:59pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/17 "2025-09-18T17:59:52Z")
> [@timothy](#): > > I wonder if you could specific in a View which entity view to open? This has always been my vote. I love this release but will only be able to use it in a couple spots. The majority of places I want this would only work in the opposite direction. Dictating entity view by the view you open it from. Basically when creating a view, selecting the entity view to open in the levels configuration. This would be a game changer for us ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [September 18, 2025, 6:23pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/18 "2025-09-18T18:23:50Z")
> [@mdubakov](#): > > ## Sync People Fields in integrations Can you add this for Hubspot as well? Also, ideally it would match on email address first, and then if nothing found it could use name. ---
**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\ **Post date:** [September 18, 2025, 6:27pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/19 "2025-09-18T18:27:44Z")
Nope, definitely not the only one. It’s my favorite email I get every Thursday 🙂 ---
**Author:** ![smoran](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/smoran/32/8909_2.png) [@smoran](https://community.fibery.io/u/smoran)\ **Post date:** [September 18, 2025, 8:11pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/20 "2025-09-18T20:11:55Z")
Huge impact on UX!! If you add the rules for action buttons, you guys can take the rest of the year off 😆 [Next page](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616.md?page=2)