Documentation

Resolve tag move errors caused by permissions in AEM 6.5

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

When you move a tag from one namespace to another and then move it back to its original location, the operation fails with Access denied because AEM requires temporary node creation at the taxonomy root. Grant Create on /content/cq:tags to allow the move while keeping full access restricted to your project tag path. To fix this, grant Create on /content/cq:tags and retry the move.

Description description

Environment

Product: Adobe Experience Manager (AEM)
Version: 6.5, including Service Pack 2
Constraints: Authors have full access only to their designated project tag path and read-only access elsewhere.

Issue/Symptoms

  • Moving a tag from one namespace to another within a project works as expected.
  • Moving the tag back to its original location fails with the  Access denied error.

Cause

The failure occurs because permissions are insufficient for creating temporary nodes under the root tags directory.

Resolution resolution

  1. Open the AEM User Administration console.
  2. Select the affected author user or group.
  3. Assign Create permission on /content/cq:tags.
  4. Keep full access (Read, Modify, Create, Delete, Replicate) limited to the specific project tag path the author manages.
  5. Save changes and sign in as the author user.
  6. Move the tag back to its original location within the designated project area.
  7. Verify that the move completes successfully.

Note:

  • Granting Create on /content/cq:tags enables temporary node creation needed for tag moves. It doesn’t allow modification or deletion of tags outside the author’s designated area.
  • The Create button appears at higher levels in the Tags Console. Attempts to create tags outside authorized areas fail without Modify/Delete rights.
  • For stricter separation between projects, remove Read access for other areas. This is more restrictive and affects usability.
  • If you need to hide UI elements such as the Create button for clarity, implement frontend customization. This is outside standard product configuration.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f