Use the Cache page in Sitecore Content Hub to clear specific caches in the web server environment. A cache stores active data (such as web pages, text, images, and so on) temporarily in the local cache of the environment to shorten data access times and improve performance.
To access the Cache page, on the menu bar, click Manage and, on the Manage page, click Cache.
The following cache settings are available:
Clear Navigation cache: clears the Navigation cache that stores temporary files when menu items change (for example, when changing menu tiles or home page tiles).
Clear Policies cache: clears the Policies cache that stores temporary files when user group policies and security changes (for example, when the security policies are modified for a specific user group). You must clear the Policies cache for the changes to take effect.
Clear Pages cache: clears the Pages cache that stores temporary files when the user agreement changes, or there are changes to page components and controllers (for example, when changing the facet tree with the entity manager).
Clear Option lists cache: clears the Options lists cache that stores temporary files when editing, saving, or deleting data sources.
Clear Aggregates cache: clears the Aggregates caches that store temporary files when aggregate entities of entity definitions are edited.
Clear Settings cache: clears the Settings cache that stores temporary files when delivery URLs are edited.
Translations cache: clears the Translations cache that stores temporary files when importing new portal translations.
Chili cache: clears the Chili cache that stores temporary files when changes are made to the publication type of the Chili objects.
Watermark cache: clears the Watermark cache that stores temporary files when watermarks change.
OAuth clients cache: clears the OAuth clients cache that stores temporary files when OAuth client entities change.
Click Clear all to clear all of the caches at once. When you clear the cache, Content Hub rebuilds it using data from the database, which may result in a slight dip in performance for anyone using Content Hub at that time.
Can we improve this article ? Provide feedback