Skip to main content
Adobe Employee
Nov 4, 2026 1:47 PM UTC
New

Allow Stage-to-Production content promotion for business authors in AEM as a Cloud Service

Problem
Cloud Manager Content Copy only supports copying content to non-production destinations, so Production is not available as a target. Today, moving content authored or validated in Stage to Production Author requires a content package, which needs developer permissions and must be run by the technical team.

Impact

  • Business teams, who operate AEM functionally, depend on IT to promote content between environments.
  • Time-sensitive pages, such as promotional landing pages, are built by marketing agencies under tight deadlines. Promotions often outside of IT working hours, which makes the dependency a bottleneck.
  • Preview does not fully replace Stage validation. For example, analytics tracking is not sent from the Preview service, so we cannot validate it before going live.

Idea
Provide a governed, self-service way for authorized business users to promote content from Stage to Production Author, for example:

  • Support Production as a destination in Content Copy, or an equivalent controlled workflow.
  • Make it permission-based, so it does not require developer-level access.
  • Include scoped paths, an audit trail, and a backup or rollback option.

Expected benefit
Faster time-to-market for campaign content, less dependency on technical teams, and a more efficient operating model between business and IT.

Current workaround
Authoring in Production Author, reviewing through the Preview service (which needs an IP allow list), then publishing. Alternatively, a manual content package transfer run by a developer.

1 reply

Adobe Employee
Nov 6, 2026 1:39 PM UTC

+1, and adding context from the field, as a Professional Services consultant. We see this pattern across many AEM as a Cloud Service customers, not just one. One scenario makes it especially critical is content created while validating new code.

So think about this use case:

  1. A release with new components, templates or Content Fragment Models is deployed to Dev or Stage for validation (usually Dev first)
  2. Business authors and agencies create pages, components, fragments and assets with those capabilities to validate the release functionally
  3. The release is approved and deployed to Production through Cloud Manager.
  4. The validated content cannot be promoted to Production Author. Teams have to either re-author everything in Production or ask IT to move it with content packages.
     

The recommended model (author in Production, review on Preview, then publish) works well for everyday editorial content, but it does not cover this case: until the code is in Production, the new components and models do not exist there, so the content cannot be prepared there in advance.

Also, the package (using Package Manager) workaround does not scale: teams must rely on manual content packages that need developer permissions, hit timeouts that cannot be extended (transfers of about 60 seconds, etc), grow quickly with asset binaries that may need reprocessing, risk deleting Production content, and offer no self-service or audit trail

What would make a promotion capability safe for Production (they way I see it) is to promote selected paths together with their dependencies after checking that they are compatible with the code deployed to Production; preview changes and merge them non-destructively into Production Author only, so they still go through the normal Preview → Publish flow and process assets in Production

The impact of this feature would be very beneficial, since no duplicated authoring for each release, faster go-lives, less dependency on IT, and fewer risky manual package operations in Production.

Regards,
Jose Berciano.

Translate