Launch vs Adobe Workfront

A campaign is the durable object in Launch. It owns the assets, systems, requirements, approvals, and history attached to it. The object stays the same from scan to go-live to review.

Workfront organizes work into projects, tasks, issues, and requests. Adobe’s documentation also covers Workfront Planning, reporting, and a REST API. Approvals can attach to work items, documents, and proofs.

Preflight is an automated test a campaign must pass before it is allowed to go live. It covers twenty-one requirements in six groups. No person can mark a requirement complete.

Workfront approvers make a decision on an item. Available decisions depend on the item type and include Approve, Reject, Approve with Changes, and Needs Work.

Launch asks for two approvals, always in the same order: brand, then legal. People approve. Launch records who approved, against which rule version. A committed launch is read only for everyone but the current approver.

Workfront approval processes link to a status. Approvers can be users, job roles, or teams. When a role is assigned, any team member with that role can decide. Approval changes the item’s status. A rejection resets the status or creates an issue, depending on configuration.

Launch rules cover brand, language, claims, legal, and accessibility. Rules are versioned. Every evaluation names the version that produced it. Exceptions are scoped, owned, tied to a rule version, and time bound.

Workfront administrators create approval processes at system level, group level, or for a single use. Adobe documents these as the way to standardize how work is reviewed.

Scan checks what is live across a company’s public web presence and connected systems. A domain scan needs no account and no credentials. A team can see how live assets differ from what was approved.

Workfront provides reports and dashboards over work items, and Adobe documents task reports and dashboards. Workfront tracks the status of the work.

Every Launch integration is read only, except Slack messaging, which the customer enables. Scan and Preflight read from connected systems. See the integrations page for what is connected today.

Workfront Fusion is a process automation tool. It links actions across apps into scenarios. Adobe lists connectors for Adobe, Google, and Microsoft applications, plus Salesforce, Jira, and Slack, and generic connectors for services with public APIs.

Every action is written to an append-only log with the actor and a timestamp. Minimum retention is two years. Exports are logged under the exporting user.

The Workfront system audit log is created for administrators. It records date and time, user name, action, object, details, and IP address. Entries cover changes from the past 90 days. Adobe documents CSV export.

Approvals belong to named people. Launch records who acted and when. Read the Launch security page for current controls. This page states no certification.

Workfront approvals are assigned to users, roles, or teams, and users with Manage permissions attach processes to items. Confirm current security controls and certifications in Adobe’s own documentation.

Scan checks and Preflight evaluates without anyone asking. People decide, and people fix content where it lives. Launch reports; it does not change your systems.

Workfront Fusion automates routine tasks through scenarios. Proofs can also use automated workflow stages that notify reviewers when it is their turn.