# Remembering page width **URL:** \ **Category:** Ideas & Features\ **Created:** [November 17, 2022, 9:51pm UTC](https://community.fibery.io/t/remembering-page-width/3547 "2022-11-17T21:51:47Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [November 17, 2022, 9:51pm UTC](https://community.fibery.io/t/remembering-page-width/3547/1 "2022-11-17T21:51:47Z")
I need wide view to be automatic when I open the page. This page feature should be a fixed page option. Thanks. ---
**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:** [November 17, 2022, 10:46pm UTC](https://community.fibery.io/t/remembering-page-width/3547/2 "2022-11-17T22:46:29Z")
Do you mean that you want Documents to always open in wide view? ---
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [November 18, 2022, 2:24pm UTC](https://community.fibery.io/t/remembering-page-width/3547/3 "2022-11-18T14:24:47Z")
Yes I do. I would like to choose the wide view for a document. And every time I open the document, it automatically has to take the wide view. Thanks. ---
**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:** [November 18, 2022, 2:29pm UTC](https://community.fibery.io/t/remembering-page-width/3547/4 "2022-11-18T14:29:37Z")
Do you ever use narrow view? It sounds like you want it to remember your choice ---
**Author:** ![ESGdataBoi](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/esgdataboi/32/11960_2.png) [@ESGdataBoi](https://community.fibery.io/u/ESGdataBoi)\ **Post date:** [November 18, 2022, 9:15pm UTC](https://community.fibery.io/t/remembering-page-width/3547/5 "2022-11-18T21:15:53Z")
I have wanted this too, but never got around to asking. But yeah, I use wide-view 99.9% of the time and am moderately annoyed at having to click that button each time I open a document. I’d LOVE a global default setting, but short of that I’d also be quite happy if the only change was the particular document remembers my page width selection when I close out and come back next. ---
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [November 19, 2022, 6:14pm UTC](https://community.fibery.io/t/remembering-page-width/3547/6 "2022-11-19T18:14:27Z")
Or a global option (wide Y/N, at level workspace) for all document, or Fibery remember my choice for each document. I use always wide view. Thanks. ---
**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:** [November 20, 2022, 4:18am UTC](https://community.fibery.io/t/remembering-page-width/3547/7 "2022-11-20T04:18:25Z")
Here’s what I’d ideally want: - Global workspace default (i.e. for all newly created docs, they are wide or narrow at the start) - Admin per-document “switch” (i.e. Admin can set each doc to a particular state that _every_ user will see upon first opening that doc) - User can maybe optionally switch to their preference _per-document_, for only them, and it persists for only them ---
**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\ **Post date:** [November 21, 2022, 4:57pm UTC](https://community.fibery.io/t/remembering-page-width/3547/8 "2022-11-21T16:57:55Z")
@Oshyan I agree that an approach like this should be favored (maximize utility and adjustability of Fibery). I feel as if there is too much focus on “use cases”, giving the impression that if you cannot justify a use case, the implementation will never happen. In my opinion everything that empowers Fibery and is low-cost to implement should be implemented. ---
**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:** [November 21, 2022, 5:14pm UTC](https://community.fibery.io/t/remembering-page-width/3547/9 "2022-11-21T17:14:22Z")
> [@Eren\_Turgut](#): > > In my opinion everything that empowers Fibery and is low-cost to implement should be implemented. Unfortunately, there is a large backlog of features to work on, so there is no such thing as ‘low-cost to implement’ - or rather, any feature has to be considered in the context of all the other features that will _not_ be worked on as a result. The focus on use case is not mutually exclusive with utility and adjustability - in fact, quite the reverse. Fibery’s focus is on adding features with an eye on the ‘bigger picture’. If you haven’t already, i would suggest reading this article by Aton: > **[Enhancing prioritization with networks](https://uxdesign.cc/enhancing-prioritization-with-networks-894760555b04)** > > Prioritization formulas measure features in isolation, missing on powerful network effects. Luckily, there is a fix. It kinda explains how a feature that appears to be low-effort/high-impact may not necessarily be the best thing to work on when taking into account network effects. Having said all that, I personally do think that a user’s page width choice should be remembered! 🙂 ---
**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\ **Post date:** [November 21, 2022, 5:41pm UTC](https://community.fibery.io/t/remembering-page-width/3547/10 "2022-11-21T17:41:31Z")
> [@Chr1sG](#): > > Unfortunately, there is a large backlog of features to work on, so there is no such thing as ‘low-cost to implement’ - or rather, any feature has to be considered in the context of all the other features that will _not_ be worked on as a result. This is exactly what I expected the reality of the things look like. I will check the article out, thanks!