Show Menu

Asset Sourcing overview

Asset Sourcing
allows the AEM users (administrators/non-admin users) to create new folders with an additional
Asset Contribution
property, ensuring the new folder created open to asset submission by the Brand Portal users. This automatically triggers a workflow which creates two additional sub folders, called
, within the newly created
folder. The AEM administrator then defines the requirement by uploading a brief about the types of assets that should be added to the contribution folder, as well as a set of baseline assets, to the
folder to ensure BP users have the reference information they need. The administrator can then grant active Brand Portal users access to the contribution folder before publishing the newly created
folder to Brand Portal. Once the user is finished adding content in the
folder, they can publish the contribution folder back to the AEM author environment. Please note that it may take a few minutes to complete the import and reflect the newly published content within AEM Assets.
Additionally, all existing functionality remains unchanged. Brand Portal users can view, search, and download assets from the contribution folder as well as from the other permitted folders. And administrators can further share the contribution folder, modify properties and add assets to collections.


  • AEM 6.5.2 or above.
  • Ensure that your AEM Assets instance is configured with Brand Portal. See, Configure AEM Assets with Brand Portal .
  • Ensure that your Brand Portal tenant is configured with one AEM Assets author instance.
Asset Sourcing is not supported on AEM Assets as a Cloud Service.

There is a known issue in AEM 6.5.4. Brand Portal users are not be able to publish contribution folder's assets to AEM Assets on upgrading to Adobe Developer Console.
The issue is fixed in AEM 6.5.5. You can upgrade your AEM Assets instance to the latest service pack AEM 6.5.5 and upgrade your configurations on Adobe Developer Console.
For immediate fix on AEM 6.5.4, it is recommended to download the hotfix and install on your author instance.