Brand Portal DRM prompt does not appear or appears unexpectedly due to asset metadata

Last update: July 7, 2026

In Brand Portal, asset downloads can start without a license prompt or show one unexpectedly when DRM metadata is missing, conflicting, or unreachable. The behavior depends on metadata such as adobe_dam:restrictions and xmpRights:WebStatement, and xmpRights:WebStatement takes precedence when both exist. Verify the applied metadata schema, correct the DRM metadata values, republish the asset, and test the download again.

Description description

Environment

Adobe Experience Manager Assets Brand Portal
Adobe Experience Manager as a Cloud Service (AEMaaCS)
AEM Assets Essentials

Issue/Symptoms

Brand Portal starts the asset download immediately with no license or terms prompt, even though DRM should apply.
Brand Portal always shows the DRM popup even when users do not expect it.
The DRM prompt works for some assets but not for others.
The xmpRights:WebStatement field breaks the expected DRM behavior when it is populated incorrectly.
Using a URL parameter such as &licenseCheck=false does not bypass DRM behavior.

Cause

Brand Portal and AEM Assets determine license-protected download behavior entirely from asset metadata. If adobe_dam:restrictions or xmpRights:WebStatement is missing, incorrectly populated, inaccessible, or conflicting, Brand Portal does not display the expected license prompt. When both fields exist, xmpRights:WebStatement takes precedence. Improper metadata schema configuration can also prevent the required fields from appearing in the asset properties, and Brand Portal cannot resolve internal or non-public URLs for xmpRights:WebStatement.

Resolution resolution

To resolve missing or unexpected Brand Portal DRM prompts, follow these steps:

Open the asset properties in AEM Author and determine whether DRM is controlled by adobe_dam:restrictions, xmpRights:WebStatement, or both.
If the required DRM field is not visible, open Tools > Assets > Metadata Schemas, edit the schema assigned to the asset folder, and add the required field.
If you use adobe_dam:restrictions, enter the intended DRM or terms HTML and save the asset metadata.
If you use xmpRights:WebStatement, make sure the value points to a fully public https:// URL that Brand Portal can access without authentication.
If xmpRights:WebStatement contains an unintended value, remove it so it does not override adobe_dam:restrictions.
Republish the asset from AEM Author to Brand Portal.
Download the asset in Brand Portal and confirm that the DRM prompt appears only when intended and displays the correct content.
If the metadata saves correctly in AEM but is not reflected in Brand Portal after republishing, contact Adobe Support.

recommendation-more-help

experience-cloud-kcs-help-kbarticles