Workfront and AEM Assets: review loops, rights and metadata
Connect Adobe Workfront and AEM Assets so requests, reviews and approvals flow into the DAM where approved assets, metadata and usage rights live.
The short answer
Integrating Adobe Workfront with AEM Assets joins the work to the content: Workfront manages requests, reviews and approvals, and AEM Assets stores the approved assets with the metadata and usage rights every channel relies on.
Prolifico Digital configures the connection, maps Workfront fields to AEM metadata and sets folder permissions as part of a Workfront or AEM Assets Quick Launch.
The content supply chain, step by step
Workfront manages the work. AEM Assets holds the approved content.
| Stage | Where it happens | What Prolifico configures |
|---|---|---|
| Request | Workfront intake forms and queues | Request types, required fields, routing and owners. |
| Create | Creative Cloud and AEM Assets | Asset storage, versioning and the Creative Cloud connection. |
| Review | Workfront proofing and review loops | Reviewer roles, proofing steps and due dates. |
| Approve | Workfront approval gates | Approval paths by content type, with status recorded against the asset. |
| Govern | AEM Assets metadata, rights and permissions | Metadata schemas, usage rights fields, folder permissions and groups. |
| Deliver | AEM Assets, Content Hub, Dynamic Media and AEM Sites | Distribution to internal and external teams and to your channels. |
Review loops that finish faster
A review loop is the cycle of feedback and revision a deliverable goes through before it is approved. The usual problems are reviewers working in email, unclear versions and approvals nobody can trace.
With Workfront and AEM Assets connected, reviewers comment on the proof in one place, decisions are recorded, and the approved version is the one that lands in the DAM.
- One place for feedback instead of inboxes and chat threads.
- Approval gates by role, so legal, brand and regional reviewers each see what they need to.
- An audit trail of who approved what and when.
- Fewer duplicate versions, because teams pull the approved asset from the DAM.
Rights and metadata that travel with the asset
The fields you choose in discovery decide how well search, reuse and governance work later.
Metadata is what makes an asset findable and safe to use. Prolifico maps Workfront fields to AEM Assets metadata so the two stay coordinated when either one is updated.
| Metadata type | Examples | Why it matters |
|---|---|---|
| Descriptive | Title, product, campaign, audience, channel. | Search and reuse across teams. |
| Usage rights | Licensed use, regions, expiry dates, approved-use notes. | Keeps expired or restricted content out of circulation. |
| Approval status | Draft, in review, approved, retired. | Shows which version is safe to publish. |
| Workfront references | Project, request or campaign identifiers. | Connects the asset back to the work that produced it. |
| Technical | Format, dimensions, resolution. | Drives renditions and delivery. |
Approved-materials workflows for governed teams
Approved versus draft, enforced by folders and permissions.
Public agencies, health systems and financial firms often need only approved material to reach staff, partners or the public. A common pattern:
- Drafts live in restricted folders; only reviewers and creators can see them.
- Approval in Workfront moves the asset to an approved folder and updates its metadata.
- Permission groups by folder decide who can search, download or share.
- Content Hub gives internal and external teams access to finished assets with the right level of access.
A county communications office is a good example: staff need the current approved flyers, forms and logos, and nothing else.
How Prolifico implements the integration
Delivered as an optional service with a Workfront or AEM Assets Quick Launch.
Discover
Map the request-to-publish process, the approvers and the metadata and rights information you need.
Configure
Connect the Workfront and AEM instances, map metadata, and set up groups and folder permissions.
Validate
Run the flow end to end with creative teams and reviewers, then fix gaps before launch.
Launch
Train users, go live and plan improvements. Ongoing support is available for both platforms.
What to have in place
- Workfront and AEM Assets entitlements, or a plan to provision them.
- An owner for the metadata model and for usage rights information.
- A list of content types and the approvers each one needs.
- Your single sign-on decision, if users will sign in through your identity provider.
- Who will administer both platforms after launch.
Keep exploring.
Workfront implementation partner
Discovery, configuration, enablement and launch for marketing and creative teams.
Learn moreWhy add Content Hub to AEM Assets
How Content Hub extends the DAM to partners and external teams.
Learn moreConnect your creative work to your DAM.
Tell us how content moves today and we'll sketch the integration.
Frequently asked questions
Can Workfront integrate with AEM Assets?
Yes. A native Workfront and AEM Assets integration is an optional service in Prolifico's Workfront and AEM Assets Quick Launches. It connects requests, reviews and approvals to the DAM. About Workfront implementation.
What metadata can be kept in sync between Workfront and AEM Assets?
Prolifico maps the fields you choose, such as campaign, project or request references and approval status, so Workfront metadata is stored in AEM Assets and kept coordinated when it changes.
How do we keep expired or unapproved assets from being used?
Store usage rights and approval status as metadata, restrict drafts to limited folders and use permission groups by folder, so only approved assets are visible to wider audiences.
Can approved assets be shared with outside teams?
Yes. Content Hub lets you securely distribute finished assets to internal and external teams, with access tailored to the right folders.
Do we need both Workfront and AEM Assets?
The integration needs both. Many teams launch one first and add the other; Prolifico can sequence the work so the integration is ready when both are live.
How much does Workfront setup (Quick Launch) cost?
A Workfront Quick Launch starts at $25,000, a one-time fixed fee, over about 8 weeks. Workfront ongoing support starts at $12,000 per quarter. What affects the price: Connections to commerce, CRM, marketing automation, identity or analytics systems add integration and testing effort. The number of users, roles and sessions for training and documentation. Generate a proposal or contact us for a quote.