Community Manager

Adobe Workfront Experts on Workfront System Smarts & Strategic Starts

Forum|Forum|4 months ago
September 22, 2025
32 の返信
12332 ビュー

October 29th, 2025

We are happy to welcome Monique Evans, Kiersten Kollins, Nichole Vargas, Cynthia Boon and Leslie Spier for an AMA session about Workfront System Smarts & Strategic Starts.

Our experts:

Monique Evans is a Senior Manager - Global Content Studio Operations at Stanley Black & Decker, Inc.
Kiersten Kollins is a Marketing Operations Tech Manager at DSW Designer Shoe Warehouse
Nichole Vargas, Leslie Spier & Cynthia Boon are Customer Success Managers from Adobe.

How this AMA works:

This thread will open on Wednesday, October 29, for you to start submitting your questions
Reply to this post with any questions you have for our Experts. They will reply to as many of your questions as possible.
After the AMA is over, the thread will be locked for new replies, but it will remain visible as a resource.

Workfront

前の返信を表示

MonicaDi4

Level 2

When delegating work, it would be awesome if we could delegate back up contacts by portfolio. I know it's not a system function (yet - not sure if it ever will be) is there a custom way to work around this?

Lyndsy-Denk

Community Advisor

For projects, we have a custom form that includes a field we called "Project co-owner." I don't see why you couldn't use the same idea: add a custom form to the portfolio with a field to define the co-owner.

S

ShannaBo

Level 2

We are seeking a solution for managing content that is initially created in English and then translated into one or more additional languages. Our primary concern is how to structure the workflow so that each translation is tracked as a deliverable, while ensuring that the metadata remains consistent and accurately reflects the relationship to the original English version. Specifically, when transferring these documents from the AEM linked folder (via the AEM native connector) to the DAM (Content Hub), we want to maintain a clear connection between the original and its translations. However, we are concerned that having multiple deliverables may lead to inconsistencies or duplication within the metadata. Ideally, the metadata should reflect both the unique aspects of each language version and the overarching project relationship.