# 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:** 14\ **Page:** 2
**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, 8:14pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/21 "2025-09-18T20:14:26Z")
What exact rules you personally need? 🙂 ---
**Author:** ![nathan\_jay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathan_jay/32/11899_2.png) [@nathan\_jay](https://community.fibery.io/u/nathan_jay)\ **Post date:** [September 18, 2025, 11:21pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/22 "2025-09-18T23:21:11Z")
> [@mdubakov](#): > > What exact rules you personally need? 🙂 I don’t know if this is what the OP meant but for me its the conditional display and conditional disable of buttons. i.e. the ability to structure conditions which make the buttons visible/hide and/or disabled. This is massive to stop users triggering actions that they really shouldn’t until some conditions are met. Ideally the conditions would work exactly like filters using all the linked entities etc however, even if its only based on fields of the entity itself it would be extremely helpful. This is implemented very well by Fillout for example. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/ed3154a98797ae52fa7687f8e1e85a8bc43c56e6.png) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/90a7753aa7c43a7d9a58fc7509e7da9781efdfe6.png) ---
**Author:** ![didier](https://avatars.discourse-cdn.com/v4/letter/d/41988e/32.png) [@didier](https://community.fibery.io/u/didier)\ **Post date:** [September 19, 2025, 7:12am UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/23 "2025-09-19T07:12:57Z")
| ![laugh](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3add1896b84e464c2489604c84d18ecd3a5c4aee.png) | Didier Lahay reacted to your message: | ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [September 19, 2025, 10:06am UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/24 "2025-09-19T10:06:00Z")
This is our main need as well, regarding rules for entity views. A couple examples. For our wiki, we’d love to have one view for document/entity editors and another view for everyone else. For the second example, we have two departments sometimes working on the same entity, but have different fields that are relevant for them. Setting view by user role would allow this to work very well. ---
**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 19, 2025, 11:44am UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/25 "2025-09-19T11:44:41Z")
> [@Michael\_Ichter](#): > > For our wiki, we’d love to have one view for document/entity editors and another view for everyone else. This is/was already possible - if no rules apply, and a user chooses an entity view, then this will be remembered for all entities of that type. So once your ‘editors’ have chosen the entity view they prefer, Fibery will remember that. Anyone else can just stick with the basic entity view (or choose one that they like). ---
**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\ **Post date:** [September 19, 2025, 4:07pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/26 "2025-09-19T16:07:42Z")
> [@mdubakov](#): > > Specify which Entity View to open based on some field value One piece of feedback: While editing a rule it would be nice to have an option of “Pin if Active” which would Pin the view in order that the views were arranged. This would allow the vies that are not relevant to stay hidden in the more views dropdown and the View that is relevant to be with the other tabs. Current ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f03b4f7afc18040da3c7b0ff133ad999efa95ffa.png) Proposed ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/62de5e5ee5b82b373070cdb6c1e45ef3feab603c.png) ---
**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:** [September 22, 2025, 5:05pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/27 "2025-09-22T17:05:36Z")
> [@mdubakov](#): > > - **Different project types.** Open a tailored view for Integration, Service, or Maintenance projects—each with its own fields and relations. > - **Tasks that change context.** Show different information when a task belongs to different projects or teams. > - **Accounts by type.** Show a focused set of fields for Client, Vendor, or Partner accounts. I always love quality of life improvements. Thanks for fitting this one in this quarter! ---
**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:** [September 23, 2025, 4:16pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/28 "2025-09-23T16:16:10Z")
![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/edf98ac4984f0028fa9a0a45ba2adfd24275f755.png) You guys, the Clockify extension revisions are live!!! Y’all are the best 💗 ---
**Author:** ![jproby](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jproby/32/12824_2.png) [@jproby](https://community.fibery.io/u/jproby)\ **Post date:** [September 24, 2025, 8:26am UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/29 "2025-09-24T08:26:03Z")
Hello and congratulations on these updates! The product’s evolution is truly a model of success. I’ve already had the chance to tell you this, but each time you manage to deliver exactly the improvements we need, even without us asking. The latest one is this ability to open a view based on some field value. I’d like to share two more general thoughts about the product, in case they might be useful. The first concerns the Whiteboard. As a Figjam user since the beginning, I didn’t really see the point of this feature in Fibery, which always seemed a step behind in terms of functionality. We help our clients define target functional architectures and quite often need to document their processes, financial flows, functional or application architectures through diagrams. Of course, there are specialized tools, but none really cover our needs. With Figjam (or PowerPoint…), the difficulty is often the same: we present the same information from different, interconnected perspectives. If we need to update or add information, all diagrams and presentations potentially need updating. The risk of inconsistencies is high, and many representations quickly become obsolete. This is where Fibery seems to make a real difference by linking data and graphical representations. To get the most out of it, however, we are missing at least two functions that exist in classic views: the ability to filter the entire board based on criteria, and the ability to add color codes to entities displayed, based on criteria. I don’t know if this is the direction you want to take the Whiteboard, but it seems to me this is where you could stand out from other tools. My second point is more about sharing a trend we notice among our clients, which might help you in the difficult positioning of your solution. We mainly work for asset management companies or private banks of significant size, which therefore have substantial resources. Since I started working, some vendors have unsuccessfully tried to offer RAD-type solutions, which always ended up stuck between more robust answers from IT departments and Access or Excel directly used by business teams. In recent years, vendors like Anaplan (mainly) or Pigment, positioned on planning and budgeting, have managed to establish themselves directly with business teams, with little (or no) involvement from IT. Although not originally designed for this, their flexibility in design and intelligent modeling approach mean I see many teams relying on such solutions far beyond their initial purpose of planning and budgeting. It may seem surprising to compare these solutions to Fibery, since they are built around multidimensional data engines more suited to consolidation or planning, in any case for more analytical use but they are actualy used to support all kind of business processes. Fibery is originally more “relational,” but I wonder to what extent, or how, it could address more analytical / multidimensional / calculations needs, beyond what “Reports” currently offer. For example, I’m not sure calculated fields (which are the main way to build dynamic aggregations) would perform well with large volumes of data and it is very limited if you want to be able to analyse on different dimensions. Sorry for this overly long message, but I hope it can be useful to you. ---
**Author:** ![lars](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lars/32/7322_2.png) [@lars](https://community.fibery.io/u/lars)\ **Post date:** [September 24, 2025, 2:36pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/30 "2025-09-24T14:36:05Z")
I’m also seconding the need for user context. For example, we’re thinking about a multi-lingual content use case, where the correct tab would be determined by user’s language. ---
**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:** [November 6, 2025, 2:30pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/31 "2025-11-06T14:30:31Z")
> [@interr0bangr](#): > > Can you add this for Hubspot as well? added > [@November 6, 2025 / Contributor Space access is being deprecated, Edit entities you create, Hide empty "No parent" groups](https://community.fibery.io/t/november-6-2025-contributor-space-access-is-being-deprecated-edit-entities-you-create-hide-empty-no-parent-groups/9967): > > Contributor Space access is being deprecated Now that we have a [new](https://community.fibery.io/t/october-30-2025-share-entities-to-web-using-access-templates-new-names-for-access-levels-improved-file-fields-support-in-automations/9924) beautiful (and consistent!) set of Space access levels, we will gradually deprecate the legacy Contributor access: [image] Quick reminder: Contributors can see and comment on all entities in the Space as well as create new ones. Additionally, Contributors can edit entities they have created or are assigned to. Contributor access is an echo of dark times when you couldn’t [share a Database](https://the.fibery.io/@public/User_Guide/Guide/Share-Database-342) or [automatically share Entities with a…](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-with-assigned-People-327) ---
**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:** [November 6, 2025, 2:37pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/32 "2025-11-06T14:37:51Z")
> [@mdubakov](#): > > added 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:** [March 5, 2026, 1:28pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/33 "2026-03-05T13:28:34Z")
> [@Michael\_Ichter](#): > > This is our main need as well, regarding rules for entity views. A couple examples. For our wiki, we’d love to have one view for document/entity editors and another view for everyone else. For the second example, we have two departments sometimes working on the same entity, but have different fields that are relevant for them. Setting view by user role would allow this to work very well. Specify which Entity View to open for a user or a group released today [March 5, 2026 / 🙈 Hide Entity Views with rules, Specify which Entity View to open by default for a user, Validation rules on Create](https://community.fibery.io/t/march-5-2026-hide-entity-views-with-rules-specify-which-entity-view-to-open-by-default-for-a-user-validation-rules-on-create/10491) ---
**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:** [March 5, 2026, 1:28pm UTC](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616/34 "2026-03-05T13:28:48Z")
> [@interr0bangr](#): > > 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”. Specify which Entity View to open for a user or a group released today [March 5, 2026 / 🙈 Hide Entity Views with rules, Specify which Entity View to open by default for a user, Validation rules on Create](https://community.fibery.io/t/march-5-2026-hide-entity-views-with-rules-specify-which-entity-view-to-open-by-default-for-a-user-validation-rules-on-create/10491) [Previous page](https://community.fibery.io/t/september-18-2025-specify-which-entity-view-to-open-based-on-some-field-value/9616.md?page=1)