New Marketo emails need an approval plan before batch release

A Marketo practitioner asked whether emails made in the new Email Designer can be mass approved. The sole reply said they did not believe bulk approval was supported. That is useful release-planning evidence, but it is not a product-wide capability statement. Adobe's comparison documents the email lifecycle, while its overview says the Designer has its own asset behavior. Before a large migration, test the exact approval path in the target subscription.

Run a small tenant-level capability check

Create two non-production email assets with the new Designer. Check the Design Studio list, multi-select actions, asset menus, and the available roles. Record whether Approve appears for both at once and whether the action affects the correct version. Do not infer support from bulk approval of classic assets or landing pages. The exact asset type, IMS migration state, and permission set belong in the test record.

Estimate the release work, not just the build work

If the only supported path is per-email approval, count assets by program, owner, and release date. Assign a reviewer and an approver, reserve time for proof and re-approval after edits, and sequence dependent smart campaigns after approval. A batch can look finished in a content spreadsheet while every email remains unusable. Track asset ID, proof evidence, approver, and approval timestamp.

Avoid a dangerous shortcut

Do not use an undocumented API or borrowed classic-email script to automate new Designer approval. Adobe's overview says assets being edited via API are not supported in the new Designer at this time. Seek an Adobe-supported path or split the launch into smaller waves. Treat the community reply as a reason to test, not as a permanent platform limitation.

Adovo’s view

Approval is part of production capacity. A campaign is ready only when every required asset has passed proof and can legally run. Plan that last mile before calling migration complete.