DocumentationExperience Cloud KCS

Page reorder drag handle missing in List View in Adobe Experience Manager Sites

Last update: September 7, 2026

In Adobe Experience Manager (AEM) Sites, a user doesn’t see the page reorder drag handle in the Sites console List View, while other users with similar permissions continue to see it. This issue is often limited to a specific user and environment. To fix this issue, review user nodes, group memberships, and permissions, then remove any conflicts that affect the drag handle functionality.

Description description

Environment

  • Product: Adobe Experience Manager (AEM) Sites
  • Instance: Issue may be isolated to a specific user and environment

Issue/Symptoms

  • The page reorder drag handle isn’t visible for a user in the Sites console List View.
  • Other users with similar permissions can see and use the drag handle.

Cause

Multiple user nodes, such as a legacy local account and an IMS federated account, or conflicting permissions, including deny permissions inherited from group memberships.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Verify if the affected user has more than one user node under /home/users (for example, both a legacy local account and an IMS federated account).

  2. Compare the Access Control Entries (ACEs) for all user nodes associated with the affected user.

  3. Review the user’s group memberships and check for any deny permissions that affect the drag handle functionality.

  4. Use the impersonation feature to confirm that the drag handle is missing for the affected user, and impersonate other users with similar permissions to verify whether the issue is isolated.

  5. If applicable, disable the legacy local user node instead of deleting it immediately:

    1. Navigate to Tools > Security > Users in AEM.
    2. Locate the duplicate user account and select Edit.
    3. Change the Account status to disabled.
    4. Test whether the drag handle appears for the user after disabling the legacy node.

  6. If disabling the legacy node resolves the issue and no negative impacts are observed, consider removing the legacy node. Back up the user node and related permissions before removal. Remove the legacy user node by using the appropriate method for your deployment.

  7. If the issue persists, review and adjust ACEs for the user and relevant groups, ensuring that any changes are reversible.

  8. Document all changes made and monitor for any unintended side effects.

  9. After making changes, sign in as the affected user (or impersonate the user).

  10. verify that the page reorder drag handle is now visible in the Sites console List View.

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