Documentation

Publishing DAM folders with content fragments fails due to insufficient permissions in AEMaaCS

Last update: Tue Dec 16 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

Publishing a DAM folder that contains content fragments in Adobe Experience Manager as a Cloud Service (AEMaaCS) fails with an error about insufficient rights to manage publications. This happens when the user or group lacks required read and replication permissions on both the content fragment models and the DAM folder. To fix this, grant the necessary permissions on the relevant paths and retry publishing.

Description description

Environment

Product: Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • Publishing a DAM folder containing content fragments fails with the error: Not enough rights to manage publications.
  • The affected user or group already has jcr:versionManagement, crx:replicate, rep:write, and jcr:lockManagement permissions.
  • Publishing still fails despite these permissions.

Resolution resolution

  1. Log in to AEM Author with an admin account.

  2. Go to Tools > Security > Permissions.

  3. Select the user group that can’t publish.

  4. Add these privileges on /conf/<my_project>/settings/dam/cfm/models (replace <my_project>with your project name):

    • jcr:read
    • rep:write
    • crx:replicate
    • jcr:versionManagement
    • jcr:lockManagement

  5. Set the same privileges on /content/dam/<my_project>:

    • jcr:read (required for publishing)
    • crx:replicate
    • rep:write
    • jcr:lockManagement
    • jcr:versionManagement

  6. Save your changes.

  7. Retry publishing the DAM folder with content fragments.

  8. Verify that publishing completes without permission errors.

The jcr:read privilege is required for publishing, even if users can browse or create content fragments. Granting jcr:all also resolves this, but specific privileges are preferred for security. When you add multiple fine-grained permissions, AEM may consolidate them into higher-level ones after saving. If you use custom node types, add jcr:nodeTypeManagement on relevant paths.

Permission considerations for headless content in AEMaaCS documentation

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f