DocumentationExperience Cloud KCS

AEM as a Cloud Service: Page creation fails in specific content paths due to missing Allowed Templates configuration

Last update: July 17, 2026

This article explains how missing or misconfigured Allowed Templates settings can prevent page creation in certain content branches in Adobe Experience Manager as a Cloud Service.

Description description

Environment


Adobe Experience Manager as a Cloud Service (all versions)

Issue/Symptoms


Users assigned to a specific authoring group are unable to create pages in certain content folders, even though they have the required permissions (including jcr:read, rep:write, jcr:versionManagement, and jcr:lockManagement).

  • Page creation works under some paths (For example: /content/test/en/folder1).
  • Page creation is unavailable under other paths (For example: /content/test/en/folder2).
  • No explicit error message is shown; the Create > Page option is missing or disabled in the UI for affected paths.

Access Control List (ACL) configuration includes allow permissions on /content/test/en/folder2.

Troubleshooting confirmed:

  • Permissions are correctly assigned and inherited.
  • The issue isn’t caused by ACL conflicts, as the same ACL structure exists on both working and non-working branches.

Resolution resolution

Follow these steps to resolve the issue:

  1. Compare Allowed Templates Configuration

    • Navigate to the working content path (For example: /content/test/en/folder1/jcr:content).
    • Check for the presence of the cq:allowedTemplates property.
    • Note the templates listed in this property.

  2. Update the Non-Working Path

    • Go to the affected path (For example: /content/test/en/folder2/jcr:content).
    • Add or update the cq:allowedTemplates property to match the configuration from the working path.
    • Ensure the property lists all templates that should be available for page creation.

  3. Test Page Creation

    • Attempt to create a page under the updated path.
    • Confirm that the Create > Page option is now available and functional.

  4. Review ACLs if Issue Persists

    • If updating the allowed templates doesn’t resolve the issue, review group memberships for conflicting inherited deny permissions.
    • Test with a user only in the authoring group to rule out ACL conflicts.

Cause

The root cause was a missing or misconfigured cq:allowedTemplates property on the affected content branch, which prevented page creation despite correct permissions.

recommendation-more-help
experience-cloud-kcs-help-kbarticles