[Workfront] Vendor Image Workflow | Adobe Higher Education
Skip to main content
Level 1
March 6, 2026
Frage

[Workfront] Vendor Image Workflow

  • March 6, 2026
  • 1 Antwort
  • 12 Ansichten

Has anyone implemented a Workfront process or workflow that enables external vendors (non-licensed users) to upload imagery or other creative assets directly into a Workfront request or project?

If so, I’m especially interested in understanding:

  • How you structured the intake mechanism (e.g., request forms, external user access, proofing workflows, document sharing links, etc.).
  • How vendors submitted assets — were they uploading files directly into the request, using external proofing, or leveraging a third‑party integration?
  • Whether you built any validation rules around the imagery being uploaded, such as required file type (JPG/PNG), minimum dimensions, resolution/quality checks, maximum file size, or naming conventions.
  • How automated the process was — for example, did you use Workfront Fusion, custom API calls, or native Workfront validation options to enforce requirements?
  • Any challenges or best practices you learned from coordinating asset delivery with external contributors.

I’d love to hear about any real-world setups or recommendations for ensuring that vendors submit assets correctly and consistently within Workfront.

1 Antwort

Patrick-antegma
Level 4
March 6, 2026

Hi ​@ChrisAf,

 

This is a great question — and honestly it goes beyond a simple “yes/no” community answer. What you’re describing is essentially a small solution design effort rather than a configuration tweak.

 

We’ve helped organizations implement vendor asset-intake processes in Workfront and AEM, and the right approach really depends on:

  • Whether vendors are licensed or non-licensed users

  • Where assets ultimately need to live (Workfront vs AEM Assets)

  • How strict your validation requirements are (file type, dimensions, naming conventions, etc.)

  • How much automation you want at ingestion

There are native capabilities that can support parts of this, but in most real-world scenarios some level of automation (e.g., Fusion) or structured intake design is involved to make it scalable and governed properly.

If you’re open to it, feel free to share a bit more about your environment — or connect directly — and we’d be happy to discuss practical patterns we’ve implemented.

 

Thanks

Patrick