Differences in publish permissions in AEM Content Fragment editors
Removing the crx:replicate permission from author groups removes Quick Publish for pages but still shows the Publish action for Content Fragments in the New Content Fragment Editor. This behavior differs from the classic editor because each editor evaluates permissions differently.
Description description
Environment
Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) – Sites
Instances: Development Pre-Release environment
Issue/Symptoms
- The quick publish option is no longer available for pages.
- In the New Content Fragment editor, authors can still access and use the Publish action for Content Fragments.
- In the classic editor, the Publish button is hidden as expected.
Resolution resolution
Follow these steps to resolve this issue:
-
Understand that this behavior occurs because the classic and new Content Fragment editors implement permission checks differently.
-
The classic editor displays or hides the Publish button based on two conditions:
- You have
canReplicatepermission. - You hold a lock on the Content Fragment.
- You have
-
The new editor shows the Publish button when the user has PUBLISH permission for the specific Content Fragment and the fragment has a valid path.
-
Removing only
crx:replicatedoes not hide or disable the Publish button in the new editor, but it still blocks actual replication when no other replicate permissions exist. -
To enforce stricter publishing controls, such as workflow-based approval, configure additional permissions or workflows that align with organizational requirements.
-
After updating permissions or workflows, verify that publishing behavior works as expected in both editors.
Additional information
The classic and new Content Fragment editors use different permission checks. Removing the crx:replicate permission does not hide publishing options in the new Content Fragment editor, but it still blocks actual replication when no other replicate permissions are granted.