Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
BACKGROUND
Starting in Strategy 10.11, users are able to create personalized caches for dossiers accessed through Strategy Library. Library and bookmark caches improve performance by caching the individual pages in dossiers and the personalizations applied to them by end users. The information cached will include manipulations applied to dossiers by end users (such as sorting) and the chapter last accessed by the user before the dossier was closed. A full discussion of Library caching can be found in KB440586.
QUESTION
Consider the following scenario:
Library caching is disabled for a particular project through Strategy Workstation as seen below:

A user logs into Strategy Library and opens DossierA and views the default chapter, Chapter1. The user browses to a different chapter, Chapter2, and modifies the sort order for the grid in Chapter2. The user then exits the dossier and logs out of Library.
Will the manipulations performed above be preserved the next time the user opens DossierA even though Library and bookmark caching is disabled? That is, the next time the user opens the dossier, will the first chapter displayed to the user be Chapter2, and will the grid in Chapter2 retain the sort order applied to it during the previous session?
ANSWER
Yes. In the scenario described above, the user will see Chapter2 and the modified sort order when they next open the dossier in Library. The personalized manipulations performed on a dossier in Library are recorded in the metadata. Users should note that the manipulations performed in Library are not modifying the base object definition of the dossier in the metadata. Rather, the manipulations are recorded in the Change Journal tables and leave the base object definition unchanged.
If Library and bookmark caching is not enabled, then this personalization information will be retrieved from the metadata and personalized views will still be preserved for users. However, users should be aware that there is a performance benefit to caching the personalization information.