How it works
An Asset Hub is a block you add to a portal experience that lists assets from your library. There are two kinds: a general Asset Hub that shows org library assets filtered by the folders you include, and a partner-specific Asset Hub that shows only the assets tied to the partner viewing it. You configure the hub in a sheet that controls layout, visible properties, sorting, saved views, and which asset folders are included. Library visibility still applies, so partners only see assets they are allowed to. Views inside the hub are tracked, so engagement appears alongside your other asset analytics.Prerequisites
- Write access to experiences.
- Assets organized in the library, ideally in folders you can include or exclude.
Settings & configuration
Asset Hubs are configured from within an experience in the experience builder.Adding a hub
In an experience, add an Asset Hub block (general) or a partner-specific Asset Hub block from the section picker.Layout
Choose a table or thumbnail layout, set how many thumbnails per row, and toggle search and filters so partners can find assets.Properties and sorting
Choose which properties partners see, such as name, type, categories, and last updated, and set a default sort.Views
Create named views with their own filters and sorting so partners can switch between curated slices of the hub.Asset visibility
Use the asset visibility settings to include or exclude folder paths, controlling exactly which assets appear in this hub. Library-level visibility restrictions still apply on top.Setup walkthrough
Open an experience
Go to Experience builder and open an experience.
How-to guides
Add and configure an Asset Hub in the portal
Embed a browsable, curated asset library in a partner experience, from adding the block to publishing it.
Share assets at scale with audience filters
Embed your asset library once and use audience filters to automatically show each partner only the content relevant to their tier, phase, experience, role, or CRM data.
Limits & gotchas
Troubleshooting
- An included asset is missing for a partner - the asset’s library visibility excludes them.
- The partner-specific hub is empty - no assets are tied to that partner yet.
- A configuration change is not visible - the experience was not published.