Adobe Experience Manager (AEM) Assets is a digital asset management (DAM) solution that can integrate with Adobe Creative Cloud to help DAM users work together with creative teams, streamlining collaboration in the content creation process.
Adobe Creative Cloud provides creative teams with an ecosystem of solutions and services to help them to create digital assets. It includes desktop and mobile applications, cloud services like storage with desktop sync or web experience, as well as marketplaces like Adobe Stock.
Read on to know what integrations to pick between desktop and the enterprise-grade DAM based on your use case and what are the associated best practices for the connecting workflows.
AEM to Creative Cloud folder sharing is now deprecated and no longer covered below. Adobe recommend newer capabilities like Adobe Asset Link or AEM desktop app to provide creative users with access to the assets managed in AEM.
|Simplify experience for creatives on desktop||Streamline access to asset from a DAM (AEM Assets) for creative professionals, or more broadly, users on desktop working in native asset creation applications. They need an easy and straightforward way to discover, use (open), edit and save changes to AEM, as well as upload new files.||Win or Mac desktop; Creative Cloud apps
|Provide high-quality, ready-to-use assets from Adobe Stock||Marketers help accelerate the content creation process by assisting with asset sourcing and discovery. Creative professionals use the approved assets right from within their creative tools.
||AEM Assets; Adobe Stock marketplace; metadata fields
|Distribute and share assets by organizations||Internal departments/local branches and external partners, distributors, and agencies use the approved assets shared by the parent organization. The organization wants to securely and seamlessly share the created assets for wider reuse.
||Brand Portal, Asset Share Commons
|Value proposition for the involved personas||Adobe offering||Involved surfaces|
|Creative users discover assets from AEM, open and use them, edit and upload changes to AEM, as well as upload new files into AEM, without leaving Creative Cloud apps.||Adobe Asset Link||Photoshop, Illustrator, and InDesign|
|Business users simplify opening and using assets, editing and uploading changes to AEM, and uploading new files into AEM from the desktop environment. They use a generic integration to open any asset type in the native desktop application, including non-Adobe ones.||AEM desktop app
||AEM desktop app on Win and Mac desktop|
|Marketers and business users discover, preview, license and save, and manage the Adobe Stock assets from within AEM. Licensed and saved assets provide select Adobe Stock metadata for better governance.||AEM and Adobe Stock integration||AEM web interface|
This article focuses primarily on the first two aspects of the collaboration needs. Distribution and sourcing of assets at scale is briefly mentioned as a use case. For such needs solutions, consider Adobe Brand Portal or Asset Share Commons. Alternate solutions such as AEM Assets Brand Portal, solutions that can be built based on Asset Share components, Link Share, using AEM Assets web UI should be reviewed based on specific requirement.
|Use Case||Adobe Asset Link||AEM desktop app||Remarks / Other Solutions|
|Discover - browse AEM folders||Yes||AEM Web UI + desktop actions||When browsing the network share, turn off the thumbnails to avoid downloading binary files of assets.
|Discover - access AEM collections||Yes||AEM Web UI + desktop actions|
|Discover - search for assets from AEM||Yes||AEM Web UI + desktop actions|
|Use - open asset||Yes||Yes - for any app||Open from Web UI or from Finder|
|Use - place asset from AEM into a document||Yes - embedding||Yes - linking or embedding||AEM desktop app gives access to assets as files on the local file system. These links in the native apps are represented by local paths.|
|Edit - open for editing||Yes - Check-out action||
Yes - Open action (in the network share)
|Check-out in AAL saves the asset to user's creative cloud storage account (synchronized by Creative Cloud app) by default.|
|Edit - work in progress outside AEM||Yes - Asset available in user's Creative Cloud storage account synced to desktop.||Possible - in version 1.10 there is an option to turn off automated upload of local changes to AEM.|
|Edit - upload changes||Yes - Check-in action with optional comment||Yes||
|Upload - single file||Yes - uploads current active document||Yes||Web UI Upload|
|Upload - multiple files / hierarchical folder structures||No||Yes||
Custom script / tool
|Misc - user and login||Creative Cloud user logged into Creative Cloud desktop app gets recognized (SSO)||AEM user / login||Users of both solutions count against the AEM user quota.|
|Misc - network and access||Requires access from user's desktop to AEM deployment over network||Requires access from user's desktop to AEM deployment over network
||Adobe Asset Link does not share network proxy environment.
|Misc - Migrate large number of assets||No
To support asset distribution use cases, other solutions should be considered:
- AEM Assets Brand Portal for a configurable, SaaS add-on to AEM Assets to publish assets.
- Custom solutions are created based on Asset Share Commons code base.
- AEM link share to share assets ad hoc using links.
- AEM Assets web interface with areas for external parties secured by AEM Access Control setup and with necessary IT / network configuration adjustments, giving these external users access to AEM.
AEM and Adobe Stock integration provides AEM users with the ability to search, preview, license and save, assets from Adobe Stock into AEM. Licensed and saved Adobe Stock assets have selected Stock metadata, which can be used to search for them with extra filters.
A few important points about this integration:
- When assets from Adobe stock are saved to AEM, they become a regular AEM Assets, with binary saved to the AEM repository. Some metadata related to Adobe Stock are saved for the asset in AEM, otherwise the ingestion process looks the same as for any other file. For example, if Smart Tags are active, the tags are added to these assets upon saving.
- The asset saved to AEM is a copy, not a link back into Adobe Stock.
This is a brief summary of best practices for AEM & Creative Cloud Integration. Read the rest of this document to get the detailed understanding of these.
- For creative users, working in Photoshop, InDesign, or Illustrator: Adobe Asset Link provides the best user experience, including clean handling of the Work-in-progress on assets checked out from AEM
- For simplifying access to assets from desktop for any generic file format or application: use AEM desktop app
- Understand why and when to store assets in DAM: Updates to be made available to the broader team in your organization
- Mind the volume of assets shared: If your use case is asset distribution, governance and security might be the most important aspects. Consider using tools built for doing that at scale, like Brand Portal.
- Understand asset lifecycle: Know how assets are handled in your organization by different teams
- Handle frequent saves to assets with care: Adobe Asset Link takes care of that for you with PS, AI, ID. For other applications, don't carry out work in progress tasks in mapped/shared folder unless you need all the changes in DAM
The terms used in this document may have a different meaning in other contexts. In particular, the following terms pertaining to the digital asset lifecycle are used when referring to workflows between a creative professional's desktop and DAM:
- Work-in-progress or creative work-in-progress (WIP): A phase in asset lifecycle where an asset undergoes multiple changes and is typically not yet ready to be shared with broader teams.
- Creative-ready assets: Assets that are ready to be shared with a broader team, or have been
selected / approvedby the creative team for sharing with marketing or LOB teams.
- Asset approvals: The approval process that runs for assets already uploaded to DAM, which typically includes brand approvals, legal approvals, and so on.
- Final asset: An asset that has gone through all
approvals/metadatatagging and is ready to be used by the broader team. Such an asset is stored in DAM and made available to all (or all interested) users. It can be used in marketing channels or by creative teams to create designs.
- Minor asset
update/change: A quick and small change to a digital asset. It is often made in response to a retouching or minor editing request, asset review, or approval (for example, reposition, change text size, adjust saturation/brightness, color, and so on).
- Major asset
update/change: A change to a digital asset that requires considerable work, and sometimes must be done over a longer period of time. It typically includes multiple changes. The asset must be saved multiple times while being updated. Major asset updates typically cause the asset to enter a WIP stage.
- DAM: Digital asset management. In this document, it is synonymous with AEM Experience Manager Assets, unless specifically mentioned otherwise.
- Creative user: A creative professional, who creates digital assets using Creative Cloud apps and services. In some cases, a creative user may be a member of a creative team who may use Creative Cloud, but does not create digital assets (like a creative director or creative team manager).
DAM user:A typical user of a DAM system. Depending on the organization, a DAM user can be a marketing or a non-marketing user, for example a Line-of-Business (LOB) user, librarian, sales person, and so on.
To design an efficient workflow between creative and marketing/line-of-business (LOB) teams and choose the best support capabilities, it is important to understand when and why assets are stored in DAM.
Storing assets in DAM makes them easily accessible and findable. It ensures that the assets can be leveraged by numerous users across the organization or ecosystem, which includes partners, customers, and so on.
Most organizations choose to only store assets that are relevant to the downstream marketing/LOB processes (publishing to channels like web channel via AEM Sites or other channels served by Adobe Experience Cloud - Marketing Cloud, Advertising Cloud, and measured by Analytics Cloud, providing to users/partners, and so on). In addition, organizations store assets that may be subjected to a review/approval process in DAM. This way, DAM stores mostly assets that have high chances of being leveraged, and avoids storing idle assets.
Storing assets is also subject to technical and resource utilization considerations. DAM provides additional services around stored assets, including extracting metadata, versioning, generating previews/transcoding, managing references, and adding access control information. These services consume additional time and infrastructure resources.
Often, storing all of the assets and updates is not desirable. For example, if updates to specific assets are of poor quality and consume excessive resources, the assets may not be stored in DAM.
Creative teams (and organizations) are usually not interested in storing assets at each stage of the asset lifecycle. For example, they avoid storing assets in the following cases:
- Assets that are yet to be finalized or are subject to experimentation
- Assets that fail to pass the creative/internal team review cycle
- Compared to the asset in question, the team has better candidates to represent their work to external teams
Usually, the following classes assets are stored in DAM:
- Assets that reached a certain maturity and are considered ready to be shared
- Assets that were pre-selected by the creative team
- Specific asset formats that are usable or requested by marketing, depending on a specific contract or agreement (for example, JPG files converted from RAW files, TIFFs/images from PSD originals)
As a rule, only updates to assets that are relevant to the broader set of DAM users should be stored in DAM. It ensures that users (marketing and similar functions) only see relevant versions in the DAM asset timeline.
Typically changes related to major milestones in the asset lifecycle. For example, the initial marketing-ready asset or an official update based on request/review provided by the creative team should be stored and versioned in DAM.
The creative team's update for review by the marketing team after a request for a change in the existing asset in DAM is an example of a relevant update. It should be stored and versioned in DAM for further reference or for reverting to the previous version.
The following are examples of updates that are typically not relevant:
- Early versions of assets uploaded before it is ready for marketing review
- Frequent creative changes to the asset in the work-in-progress phase before creative and marketing teams decide that the asset is ready
AEM Assets supports two types of users based on their access to the AEM Assets deployment. Typically, users inside the enterprise network (firewall) have direct access to DAM. Other users outside the enterprise network would not have direct access. The user type determines which integrations can be used from the technical standpoint.
Typically, in-house creative teams or agencies/creative professionals
In such cases, Adobe Asset Link or AEM desktop app helps provide easy access to final/approved assets and lets you save creative-ready assets to DAM.
External agencies and freelancers without direct access to the DAM instance may require access to approved assets or want to add their new designs to the DAM.
Use the following strategies to provide access to final/approved assets:
- Use desktop app if Asset Link does not work.
- Use AEM Assets Brand Portal for distributing assets securely to external partners
- Use a custom implementation of a distribution and sourcing portal based on Asset Share Commons
- Use Access Control set up in AEM and necessary network infrastructure (for example, VPN and IP whitelisting) to give external parties access to a dedicated area of content in your DAM. They can use AEM Web UI to get assets and upload new content into your DAM.
As discussed in this document, it is recommended to carry out major updates on assets, sometimes called work in progress, without having all the edits saved to the local file also uploaded to AEM as changes. This speeds up a desktop user's work, limit network bandwidth used, and keep the assets timeline clean and focused on controlled, major updates.
Adobe Asset Link offers a good support for this use case:
- When users in Photoshop, InDesign, or Illustrator intent to edit a file, they execute a Check-out operation on the given asset
- The asset is downloaded in background, put into users Creative Cloud account synchronized to disk by Creative Cloud desktop app, and the check-out flag is toggled in AEM on the asset to minimize editing conflicts
- From there on, the user works in a file that's stored locally in the synced location, and can continue working and saving necessary changes at any frequency required
- Additionally, because the asset is in the Creative Cloud account, it is also available on other devices that the user might have (for example, can be opened or edited in a dedicated Creative Cloud mobile app), and can be shared with other Creative Cloud users for collaboration purposes.
- When the creative user is done with the changes, they can execute a Check-in operation on that file in their Creative Cloud application, with an optional comment. The corresponding asset in AEM are versioned and updated to with the new binary. AEM users like Marketers or LOB users have access to major asset changes, or milestones, via AEM asset timeline UI.
AEM desktop app provides a network share for assets opened in the native app. By default, all the changes done locally are uploaded to AEM automatically after a brief while. With such a configuration, frequent saves during the work-in-progress phase would all be uploaded into AEM and versioned, creating a lot of network traffic and potential scalability challenges - not to mention unnecessary versions in AEM.
The recommended approach here is to use an option in AEM desktop app to turn off automated updates, and upload changes to assets to AEM manually, leveraging the upload changes action in the app's Asset Status UI.
You may have a requirement to simultaneously upload a larger number of files into DAM in some scenarios, for example:
- Uploading results of
photoshootsor larger projects
- Uploading assets provided by creative agencies
- Uploading selected assets from a larger set if the selection is done outside DAM
Note that this description refers to uploading files operationally (for example, every week or with every
You can leverage the following upload capabilities:
- To upload large/hierarchical folders in bulk, use AEM desktop app that provides folder upload functionality. You can also upload hierarchical folder structures. Assets are uploaded in background and, therefore, it is not tied to a web browser session
- To upload a few files from a single folder, drag the files directly to the web interface or use the Create option in the AEM Assets web interface.
- Depending upon your business requirements, you can also use custom uploaders.
If you use Network File Shares to manage digital assets, just using the network share mapped by AEM desktop app could be seen as a convenient substitute. When transitioning from network file shares, AEM web interface provides a rich set of Digital Asset Management capabilities that go well beyond what is possible on a network share (search, collections, metadata, collaboration, previews, and so on), and AEM desktop app provides a handy link to connect the server-side DAM repository with the work on desktop.
Avoid using AEM desktop app to manage assets directly in the network share of AEM Assets. For example, avoid using AEM desktop app to move/copy multiple files. Instead, use the AEM Assets web UI to drag folders from Finder/Explorer to the network share or use the AEM Assets Folder Upload feature.
To plan and execute asset migrations from existing system to a new system or migration of large volume of assets stored on servers, see the Migration Guide. AEM desktop app and AEM to Creative Cloud integrations do not support such migrations. Due to the large volumes of assets to be ingested, and additional requirements around metadata mapping, transformation, and ingestion, migrations should be handled using different tools and approaches.