AEM Cloud Service: Granting Package Manager access to non-administrative users

This article explains how to enable package creation and download capabilities for non-administrative users in Adobe Experience Manager as a Cloud Service.

Description description

Environment

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

Issue/Symptoms

By default, only users with administrator privileges can create and download packages using Package Manager in AEM. This restriction causes workflow bottlenecks, as content authors must request administrator assistance to perform package-related tasks. Standard authors are unable to access package creation tools or download packages directly in Production environments.

No specific error messages are shown; access is simply restricted based on user permissions.

Cause

By default, package creation and download permissions are restricted to administrator users in AEM. Granting specific permissions to a dedicated group allows non-administrative users to manage packages without full administrator privileges.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Verify user access to the AEM environment

    • Ensure that the users who require Package Manager access can log in to the Author instance of AEM.
  2. Create a dedicated group for package management

    • Log in as an AEM administrator.
    • Create a new group (For example: content-packagers).
  3. Grant required permissions on /etc/packages

    • Assign the following permissions to the new group:

      • jcr:read
      • jcr:modifyProperties
      • rep:write
    • Exclude delete permissions to prevent accidental package removal.

  4. Grant permissions on relevant content paths

    • Provide the necessary permissions on the content paths that users need to package.
  5. Add users to the new group

    • Add the relevant users to the content-packagers group.
    • This will allow them to access Package Manager at /crx/packmgr/index.jsp and perform package creation and download.
  6. Best practices

    • For Production environments, follow best practices by limiting package creation to authorized users and using dedicated groups to manage access.
recommendation-more-help
experience-cloud-kcs-help-kbarticles