This document provides answers to common questions about the integration and management of assets between Acquia DAM and Drupal.
Yes, users authenticate into DAM first, so their permissions match. Check the user's role permissions if they do not see the correct assets.
Assets updated in the Acquia DAM system will automatically be reflected through the cron job. Additionally, editors have the option to manually run the "Check for update" option within the Drupal application under the DAM media listing to ensure that the updated assets are quickly reflected in Drupal.
Even if the cron job runs, the assets will not automatically update in the Drupal application when the finalized version is changed in the Acquia DAM system. Editors must manually use the "Check for update" option within the DAM media listing in Drupal to ensure that the updated assets are promptly reflected in the application.
The asset metadata in the Drupal application automatically updates after the scheduled cron job runs when metadata changes are made in the Acquia DAM system. Additionally, editors can manually trigger the "Sync metadata" option from the DAM media listing within Drupal to immediately reflect the latest asset metadata updates.
The cron job automatically handles these changes by setting the assets to "unpublished" in the Drupal application.
This is currently not being handled and will be covered in the upcoming release.
Track at https://www.drupal.org/project/acquia_dam/issues/3531765
It is not advisable to delete assets from a Drupal application. If this action is taken intentionally, it disrupts the sync process, as the deleted assets cannot be restored. Consequently, the customer will need to reattach the assets to the content manually.
Currently, the supported asset types in Acquia DAM include Audio, Documents, Generic, Image, PDF, Spinset, and Video. It is not possible to extend the media sources of these types at this time.
All assets will be served directly from the local file system.
By enabling the "Download and sync assets" option.
There are two ways to import assets into the Drupal file system from Acquia DAM: you can import assets by using categories filters or by using asset group filters.
No, the administrator must select individual categories in order to import assets from each category.
No, only assets that belong to a specific category can be imported.
Yes, it supports subcategories up to 10 levels deep in the hierarchy.
No, clicking the save button only saves the configuration for importing assets for a specific category or asset groups. The cron job will process the configuration, importing the assets in batches.
No, the configuration is saved once, and the cron job automatically picks up the saved configuration. It will handle the import of any newly added assets without the need to resave the configuration.
The cron job will only import assets that belong to the saved configurations. Any removed categories or asset groups will not be considered for asset import in scheduled cron job.
The cron job imports assets in batches, so it is possible that not all assets were processed in the current run. The remaining assets will be imported during the next scheduled cron job. If you need to import the assets sooner, you can manually trigger the cron job.
Assets are served based on the media type options you have selected. If you have not enabled the "Download & Sync assets" feature, the assets will be delivered through the embed option.
For more related articles, visit:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Tue Jul 15 2025 07:50:04 GMT+0000 (Coordinated Universal Time)