Custom user groups locked in read-only mode in new Content Fragment editor in AEM
This article explains how to resolve an issue in Adobe Experience Manager (AEM) as a Cloud Service, where custom user groups are locked in read-only mode when accessing the new Content Fragment (CF) editor. This article outlines the necessary steps to adjust permissions and ensure that you can edit content fragments seamlessly in both the new and old editors.
Description description
Environment
Adobe Experience Manager (AEM) as a Cloud Service
Issue/Symptoms
Custom user groups with specific folder permissions in DAM face issues in the new Content Fragment (CF) editor, where:
- Content Fragments are locked and set to read-only mode.
- Permissions function properly in the old CF editor but fail in the new editor.
- Adding the custom group to the OOTB DAM Users group does not resolve the issue.
- ACL configurations have been verified and applied correctly using tools like the Netcentric AC Tool.
The custom user group is granted the following permissions for a specific folder in DAM:
- Read, modify, and replicate permissions.
- Access to only the designated Content Fragments, while other Fragments remain hidden from view.
Resolution resolution
-
Grant additional permissions: Ensure the following permissions are applied:
jcr:read
permission for/var
.jcr:versionManagement
permission for folders containing content fragments.- Folder-specific permissions: READ, EDIT, DELETE, RENAME, PUBLISH.
-
Test access after updates: Confirm that users can now edit Content Fragments without encountering read-only restrictions in both the old and new editors.
-
Example: Using the WKND project as an example, the permissions for a folder (https://experienceleague.adobe.com/content/dam/wknd-shared/en/magazine/arctic-surfing?lang=en):
Permissions for CF inside this folder:
“path”: “/content/dam/wknd-shared/en/magazine/arctic-surfing/aloha-spirits-in-northern-norway”,
“permissions”: [
“READ”,
“EDIT”,
“DELETE”,
“RENAME”,
“PUBLISH”]
Note: Ensure permissions are applied accurately for all required paths and Content Fragments to avoid discrepancies between different versions of editors.
By following these steps, you can resolve permission-related issues and restore seamless functionality for custom user groups in AEM’s new Content Fragment editor.