Skip to main content
Level 1
Oct 15, 2026 10:41 AM UTC
Question

Disabling Download button for Content Hub based on metadata value

We have a requirement to disable the Download option in Content Hub for specific assets based on a metadata value. 

  • Disable or hide Download button when ActivationTarget = ContentHub, and isReferenceAsset=TRUE 
  • Keep the asset’s metadata, preview, and reference information visible.

    3 replies

    Level 2
    Oct 17, 2026 6:34 AM UTC

    ​@user89357 ,

    There’s a documented way to get “visible but no download” in Content Hub: expired assets.

    In the Content Hub Configuration UI under Asset Visibility, enable Allow users to view expired assets and disable Allow users to download expired assets. Expired assets then stay visible with their preview and metadata, but can’t be downloaded.

    Per asset, expiry is driven by prism:expirationDate. A Sling scheduled job (not the Commons Scheduler on AEMaaCS) can set it for assets matching your condition (dam:activationTarget = contenthub and your reference flag).

    Things to check:

    • The toggles are global, so any genuinely expired asset gets the same treatment.
    • AEM’s expiry job also unpublishes expired assets from Publish and Dynamic Media, so confirm that doesn’t affect your reference assets.
    • The assets will also count as expired in AEM Assets itself.

    I would write custom logic to map a custom metadata field and check whether it matches a given value. When it matches, I set the prism:expirationDate (date) field on the asset. This causes Content Hub to treat the asset as expired.

    Note: for any field other than an explicit expiry date, custom logic has to be written.

    Thanks,

    Santhosh

    Translate
    user89357Author
    Level 1
    Oct 19, 2026 11:35 AM UTC

    Thank you for your reply, unfortunately this will not solve our issue, as we need to display these assets but not as an expired assets as these are valid, so we only need to prevent users to download these assets. It would help if the similar rule as for expired assets is applied. 

    Translate
    Level 2
    Oct 19, 2026 1:34 PM UTC

    ​@user89357 ,

    I think this can still be customized as a use case where an AEM backend Java class runs to identify the metadata property and uses prism:expirationDate to mark that an asset is not supposed to be downloaded. You can still display these assets, as expired assets can be displayed with the download option removed.

    However, on a larger scale, if this needs a proper custom solution, we will have to raise an Adobe ticket to get this feature worked on. Unfortunately, there seems to be no solution available out of the box for custom metadata property.

    Regards,
    Santhosh

    Translate