Acquia AI identifies approved assets in Acquia DAM when users describe requirements in plain language. Users do not need knowledge of specific metadata field names or values configured by an organization.

Asset search operations run in Work mode and consume AI credits. For additional details, visit AI credits and usage.

Prerequisites

Ensure that the setup meets the following requirements:

• The account holds Acquia AI access and Work mode permissions.

• The organization holds DAM and DAM API access.

Acquia AI identifies approved assets in Acquia DAM when users describe requirements in plain language. Users do not need knowledge of specific metadata field names or values configured by an organization.

Asset search operations run in Work mode and consume AI credits. For additional details, visit AI credits and usage.

Prerequisites

Ensure that the setup meets the following requirements:

• The account holds Acquia AI access and Work mode permissions.

• The organization holds DAM and DAM API access.

• The MCP server is enabled for Acquia DAM.

Search for assets

To find an asset:

1. Open Acquia AI, or start a chat in Acquia Source.

2. Describe required asset details, including campaign names, formats, and applicable constraints such as required usage rights.

3. Review returned results and open the matching asset.

Requests that state the asset purpose provide better context than file names. For example: A landscape hero image for a Digital Government Summit email, approved for external use.

Asset result content

Each result includes:

• Asset preview

• Metadata relevant to the query

• Usage rights, including region permissions

• Link to the asset in Acquia DAM

• Embed link ready for email templates or external tools without download steps

• Match rationale explaining why the asset met request criteria

The agent specifies the search query executed in Acquia DAM so users can evaluate result coverage.

Verify usage rights before publication

The agent displays usage rights recorded on the asset without evaluating permission for intended uses. Read recorded rights on each asset before publication, and contact a DAM administrator when rights require clarification.

Audit metadata

A DAM administrator can use the project agent to check library metadata quality. For example: List an image added in the last 30 days with no description.

The agent returns the requested list without populating empty fields. Administrators complete missing metadata in the Acquia DAM interface.

Search result considerations

The agent translates requests into Acquia DAM search queries, so results depend on search execution completeness. The agent can omit relevant assets.

Each result specifies the executed search query and match rationale to help users refine search phrasing. Administrators can re-run queries directly in Acquia DAM. For exhaustive audits, treat agent outputs as initial lists rather than complete inventories.

Agent limitations in Acquia DAM

The agent performs read operations only and does not modify resources:

• Does not edit metadata

• Does not upload or delete assets

• Does not move assets between collections

• Does not approve assets in workflows

• Does not expand permissions configured by a DAM administrator

System limits

• Application scope: Access covers the Assets application only, excluding Entries, Templates, and Workflow.

• Single account per query: Acquia activates integration for one Acquia DAM account at a time because roles apply per account. Organizations running separate accounts per brand or region receive separate agents per account. Single queries cannot search across two accounts.

• Admin-managed setup: Self-service setup is unavailable.

Asset data handling

Assets and metadata are never copied outside Acquia DAM. The agent reads data in place within the selected Acquia DAM region. Acquia does not use assets, metadata, or conversation histories to train AI models. For additional details, visit Data handling, privacy, and security.

Conversations persist for session duration and remain accessible to the initiating user.