DocumentationExperience Cloud KCS

Transferring editorial access for a page in Adobe Experience Manager

Last update: September 10, 2026

This article explains how to transfer editorial access and publishing rights for a page in Adobe Experience Manager as a Cloud Service (AEMaaCS). Organizations may need to assign page ownership to a different team or user group to support changing business requirements. To resolve the issue, review existing permissions, obtain the necessary approvals, and update access controls so the new team can manage and publish content.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)

Issue/Symptoms

  • A team or user requests full editorial access and publishing rights for a specific page.
  • Attempts to request access changes are blocked due to insufficient permissions, such as not having the required admin role.

Root cause

The need to transfer editorial control arises from business or organizational changes. Delays occur when the requester does not have the permissions required to request or approve access changes.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Identify the team or user group that requires editorial access and the page involved, for example, /content/your-site/page-path.
  2. Confirm the current team or users who have editorial control of the page.
  3. Ensure that the requestor has the required organizational approval to request access changes.
  4. If the requestor does not have the required administrative role, such as Support Admin, coordinate with an individual in the organization who has the role to submit or approve the access change request.
  5. In the AEM administration console, locate the page, review the current page permissions, add the new team or users to the appropriate groups with editorial and publishing rights, and remove or adjust permissions for previous editors according to organizational policy.
  6. Notify both the outgoing and incoming teams about the change in editorial ownership.
  7. Provide documentation or training resources to the new team, if required.
  8. Verify that the new team or users can access, edit, and publish the page as intended.
recommendation-more-help
experience-cloud-kcs-help-kbarticles