# June 13, 2024 / Automatic access for assignees, return to expanded panel

**URL:** <https://community.fibery.io/t/june-13-2024-automatic-access-for-assignees-return-to-expanded-panel/6298>\
**Category:** Changelog\
**Created:** [June 13, 2024, 6:57pm UTC](https://community.fibery.io/t/june-13-2024-automatic-access-for-assignees-return-to-expanded-panel/6298 "2024-06-13T18:57:14Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\
**Post date:** [June 14, 2024, 4:38pm UTC](https://community.fibery.io/t/june-13-2024-automatic-access-for-assignees-return-to-expanded-panel/6298/7 "2024-06-14T16:38:04Z")

</div>

My position hasn’t changed since this summary:

> [@Closing Panels on Full Screen](https://community.fibery.io/t/closing-panels-on-full-screen/3955/24):
>
> - There are two (largely mutually exclusive) mental models of panel navigation.
> - Fibery currently leans towards the model that places more value on preserving context when browsing.
> - We are not looking to overhaul the navigational model any time soon as we are focusing on other things and don’t have enough evidence to justify the effort.
> - There are cases like `aBB → aBC → AB` that are annoying no matter the model. We’ll try to fix those and see if the number of complaints goes down significantly.

We’ll see how many complaints and awkward UX session moments we’ll get after today’s update. If the issue still pops up regularly, we’ll have another go.

---

_[View the full topic](https://community.fibery.io/t/june-13-2024-automatic-access-for-assignees-return-to-expanded-panel/6298)._