Expand my Community achievements bar.

Join expert-led, customer-led sessions on Adobe Experience Manager Assets on August 20th at our Skill Exchange.

AEMaaCS | Launches | Make them available on PREVIEW service for review/approval

Avatar

Level 5

2/19/25

Request for Feature Enhancement (RFE) Summary: Enhance the launches so that they can be published to PREVIEW service so that they can be reviewed/approved by people who do not have access to AEM.
Use-case: As an editor I use launches to prepare future updates of a page separately from the current page. This prepared version needs to be reviewed and approved by people in my organization who do not have access to AEM. For them I would like to publish the launch page to PREVIEW in order to share the URL with them.

Current/Experienced Behavior:

Currently I have no chance to publish the launch page to PREVIEW. Just view-as-published is available which does not help as the reviewers do not have AEM access. Therefore the advantage that I can prepare a page without blocking the current page is gone as I have no chance to get it on PREVIEW in order to let them check from approvers. At the end I need to promote it to do so and with this I'm back on the current page and could not working separately anymore. 

See documentation for Launches: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/...

Improved/Expected Behavior: Make the option available to publish a launch page to the PREVIEW. With that I would have the chance to share a preview URL with reviewers and approvers in my organization who do not have access to AEM.
Environment Details (AEM version/service pack, any other specifics if applicable):  
Customer-name/Organization name: Carl Zeiss AG
Screenshot (if applicable):  
Code package (if applicable):  
3 Comments

Avatar

Level 1

3/24/25

Our organization requires this to be able to use the launch functionality. Most of our content owners aren't in the system, so we rely on publishing pages to preview to get business unit approval.

Avatar

Administrator

3/26/25

@lutzU 

Thanks for proposing this idea.
This has been reported to the engineering under the internal reference SITES-30299. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.
Status changed to: Investigating