Skip to main content
All CollectionsDigital Asset Management Media Library
How to control which assets are shown to Viewers on frontend guideline library pages
How to control which assets are shown to Viewers on frontend guideline library pages
Updated this week

By default, all the images you upload to backend libraries will be shown in the library to Viewers of your guideline (on the frontend).

There are three ways you can adjust which assets are shown in the guideline view of your library:

You can use different options to limit the display of certain images on the Library page of your Brand Portal.

Apply Status to Assets

Add a certain status to images and then adjust the frontend settings so images with a specific status are not shown. Then, when the assets are ready, their status can be changed so that they are shown in the frontend.

Here are those steps:

  1. Decide which status(es) should show in the frontend guideline view and which should not.

  2. In frontend, select Search Settings > Content > Workflow. Uncheck (deselect) the statuses that should not show to Viewers.

  3. In the backend Library, use bulk curation or simply select an individual asset to set the appropriate status for that asset(s). You can see the 3 places you are able to set status in the gif below (library view, asset view, and asset gear settings).

You can find more information about customizing your library in this guide:


Apply Asset Lifecycle Dates:


Or you can set an Asset Lifecycle and exclude assets that are not yet valid or are already expired from being displayed. By setting the Asset Lifecycle, you can define when it will become available in the Library pages.

You can see how to set lifecycle dates in this gif below.

Please read more about asset lifecycle here:


Use Library Targets


Another option is to use Targets for specific user groups so different groups have access to different assets. Note that Targets would make more sense for defining different levels of access for the different target audiences permanently while 2 options above are more suitable as a dynamic way to upload new assets to the backend without having them available in the Library pages at all.

To learn more about targets, please visit our guide here:

Did this answer your question?