By default, all assets you upload to a backend library will be shown to viewers on the frontend library page.
There are three ways to control which assets are shown:
For options 1 and 2, you will use a view to control visibility. Views let you define rules based on metadata such as workflow status or lifecycle that determine which assets appear on a library page. The view updates automatically as assets change, so there is no ongoing manual work needed.
Apply Status to Assets
Add a workflow status to your assets and use a view to control which statuses are visible on the library page. When an asset's status changes, the view updates automatically, with no ongoing manual work needed.
Here are those steps:
Decide which status(es) should be visible to viewers on the library page and which should not.
Create a view with a workflow status rule that includes only the status(es) you want visible — for example, "Workflow status is one of: Approved". Connect the view to your library page. Assets with any other status will be hidden automatically.
In the backend library, use bulk curation or simply select an individual asset to set the appropriate status. 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:
You can set lifecycle dates on your assets to control when they become available or expire. By default, expired or not yet valid assets are not shown to viewers on the library page.
Here's how:
In the backend library, use bulk curation or select an individual asset to set the lifecycle dates (Asset available from and Asset available until).
In your library settings, configure what happens when an asset expires. For example, you can set it to automatically apply a workflow status such as "Expired". You can then use a view with a workflow status rule to control which assets appear on the library page.
You can see how to set lifecycle dates in this gif below.
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.
Targets let you control which assets are visible to specific user groups — for example, different departments or markets. Unlike views, which filter assets based on metadata rules for all viewers equally, targets define visibility based on who is viewing.
Note: targets are best suited for defining permanent, audience-based access. The options above (status and lifecycle) are better suited for dynamically controlling which assets are ready to be seen, regardless of who is viewing.
To learn more about targets, visit our guide here: