# \[DONE\] Multiple Entity Views - automated selection 😀

**URL:** <https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554>\
**Category:** Ideas & Features\
**Tags:** entity-view\
**Created:** [October 13, 2024, 11:04pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554 "2024-10-13T23:04:27Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**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:** [May 22, 2025, 4:41pm UTC](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554/9 "2025-05-22T16:41:02Z")

</div>

> [@mdubakov](#):
>
> we do want to go for field → default entity view in future

Any general timeline on the ability to set an entity view dynamically based on a entity field/current user?

We’re trying to sell Fibery as a potential custom CRM/ERP solution to our clients but keep running into scenarios where the lack of context filtering/dynamic views is a deal breaker.

It’s common in many industries to have multiple people needing to contribute/collaborate on a project, but not all of their roles are the same and it’s virtually impossible to maintain an accurate, secure source of truth in Fibery when viewing and editing permissions are an all or nothing option. Like, it’s not out of the ordinary for a manager to need to see and edit fields that a regular employee shouldn’t, right?

Dynamic entity views based on field values, along with [Field-Level Permissions](https://community.fibery.io/t/field-level-permissions/2799) & [Field Locking](https://community.fibery.io/t/lock-fields-to-avoid-accidental-editing/8490) are essential for many businesses to seriously consider Fibery as a solution.

---

_[View the full topic](https://community.fibery.io/t/done-multiple-entity-views-automated-selection/7554)._