Inquiry about Limitations of Adobe Experience Manager Assets in AEM as a Cloud Service for a Client with Only AEM Sites

[olsalas711]

Hello Community,

I hope this message finds you well. I have a question regarding the limitations of Adobe Experience Manager (AEM) Assets in an AEM as a Cloud Service environment.

The client in question only has access to AEM as a Cloud Service Sites, and I would like to know:

1. What are the limitations or restrictions on AEM Assets functionality in this scenario?

2. Will the client be able to use all AEM Assets features, such as digital asset management, processing profile creation, integration with Adobe Creative Cloud, etc., or are there any restrictions due to only having access to AEM Sites?

3. Is there any difference in the use of AEM Assets between a client who only has AEM Sites and one who has AEM Assets as a standalone service?

I would greatly appreciate it if you could provide detailed information on this matter, as it is crucial for planning the implementation and use of AEM in this project.

Looking forward to your response.

[Albin_Issac · Accepted solution]

In my understanding, AEM Assets fall into two categories:

1. Enterprise DAM (AEM Assets) – A full-featured Digital Asset Management (DAM) system that requires a separate license. It includes advanced functionalities such as:

   • Sharing assets with external systems.
   • Customizable metadata schemas.
   • Workflow automation for asset processing and approvals.
   • AI-powered features like smart tagging (Adobe Sensei).
   • Integration with Adobe Creative Cloud and other platforms.

2. Media Library – Comes bundled with AEM Sites (no separate license required). It is primarily for storing website-related assets but lacks advanced DAM capabilities, such as:

   • No external sharing or advanced integrations.
   • Limited metadata management.
   • No workflow automation or AI-based enhancements.

I recommend confirming these details with Adobe before making a final decision.

Regards,
Albin