AEM Assets + Workfront: Streamlining Creative Operations

The Creative Operations Challenge

Marketing teams face a common challenge: creative work happens in one system (Workfront) while final assets live in another (AEM Assets DAM). The result? Manual uploads, lost metadata, version confusion, and time wasted on administrative tasks instead of creative work.

The AEM Assets Workfront integration solves this by creating a bi-directional connection between project management and digital asset management.

Why Integrate AEM Assets and Workfront?

How the Integration Works

The AEM Assets Workfront connector creates a bridge between the two systems:

Key Integration Features

Folder Linking

The core capability is linking Workfront projects to AEM folders. You can:

• Link existing AEM folders or create new ones from Workfront
• Link multiple folders per project (e.g., /final, /source-files, /working)
• Control who can create/link folders based on Workfront permissions

Metadata Mapping

Map Workfront custom fields to AEM metadata schemas:

• Project fields — Campaign name, brand, business unit
• Document fields — Asset type, usage rights, expiration date
• Task fields — Deliverable type, channel, market

Event Subscriptions

Configure what triggers sync operations:

• Document upload — Sync when files are uploaded to Workfront
• Status change — Sync only when documents reach "Approved" status
• Project completion — Batch sync all deliverables when project closes

Bi-Directional Linking

The integration isn't one-way. From AEM, you can:

• View linked Workfront project details
• See which task/deliverable an asset came from
• Navigate back to Workfront for context

Implementation Considerations

Prerequisites

• AEM Assets — AEM as a Cloud Service or AEM 6.5 with enhanced connector
• Workfront — Enterprise or Business tier with API access
• Adobe IMS — Both systems integrated with Adobe Identity Management

Folder Structure Strategy

Before integrating, plan your AEM folder structure:

• By project — /content/dam/projects/[project-name]/
• By brand/campaign — /content/dam/[brand]/[campaign]/[year]/
• By asset type — /content/dam/images/, /content/dam/videos/

The right structure depends on how assets will be reused. Campaign-based structures work for one-off assets; type-based structures suit reusable brand assets.

Permission Alignment

Ensure permissions are consistent across systems:

• Workfront users who can create folders need appropriate AEM group membership
• AEM folder permissions should reflect Workfront project access
• Consider read-only AEM access for Workfront users who just need to reference assets

Common Use Cases

Campaign Asset Production

A marketing campaign involves multiple deliverables: hero images, email banners, social ads. Each is a task in Workfront. As designers complete and get approval, assets automatically populate the campaign's AEM folder, ready for the web team to build the landing page.

Brand Portal Updates

Brand teams use Workfront to manage logo refreshes, style guide updates, and template creation. Approved assets sync to AEM Assets, which powers the brand portal via AEM Asset Link or Brand Portal, ensuring stakeholders always access current brand materials.

Product Photography

E-commerce teams coordinate photo shoots through Workfront. Photographers upload images, creative directors approve, and product shots sync to AEM with SKU metadata—ready for automatic placement in product detail pages.

Getting Started

1. Audit current workflows — Document how assets move from creation to DAM today
2. Define metadata requirements — What fields need to transfer?
3. Plan folder structure — How should assets be organized in AEM?
4. Configure the connector — Install, authenticate, and set up mappings
5. Pilot with one team — Test with a real project before broad rollout
6. Train users — Show creatives the new workflow