Content Fragments - Delete Considerations
Some Content Fragment functionality requires the application of AEM 6.4 Service Pack 2 (184.108.40.206) or later .
Permissions - Delete or Not Delete
The ability to delete content is powerful, but potentially sensitive, with many industries needing to restrict and control how these privileges are distributed.
With regards to delete permissions, Content Fragments must be considered at two levels:
- The Content Fragment as a single entity.
- Use case : A user who needs to edit/update a content fragment - and delete an entire fragment .
- The multiple sub-entities that make up a content fragment; for example, variations, sub-nodes.Basic operation of the content fragment editor requires that such transient sub-elements can be deleted. For example, when manipulating variations; also when editing metadata or managing associated content.
- Use case : A user who needs to edit/update a content fragment - without being allowed to delete an entire fragment .
- Permissions : See Permissions Required for Editor Functionality Only .
When a user does not have any Delete permissions, the Content Fragment editor operates in read-only mode.
Permissions Required for Editor Functionality Only
For users that need to edit/update a content fragment, without allowing them to delete an entire fragment , specific permissions must be assigned, as basic operation of the content fragment editor requires that transient sub-elements can be deleted.
For example, when manipulating variations; also when editing metadata or managing associated content.
The delete permissions, required to edit/update a Content Fragment, are included in the Delete permission assigned through User and/or Group Management .
The permissions needed to edit/update a fragment need to be applied to either the node containing the content fragment, or an appropriate parent node (at any level under /content/dam ). When assigned to such a parent node, the permissions will be applied to all nodes within that branch.
For example, a folder that will hold all content fragments, such as:
Setting the permissions on /content/dam is also possible, as all content fragments are stored here.
However this action applies the same delete permissions to all other asset types as well.
The permissions prerequisite to allowing a specific user and/or group to edit/update a content fragment are:
This list shows all the privileges required, not just the delete privileges.
- For the Content Fragment nodes or folders:
- jcr:addChildNodes , jcr:modifyProperties
- For the jcr:content node of all Content Fragments:
- jcr:addChildNodes , jcr:modifyProperties and jcr:removeChildNodes
- For all nodes below jcr:content of all Content Fragments:
- jcr:addChildNodes , jcr:modifyProperties and jcr:removeChildNodes , jcr:removeNode
These remove privileges must be administered using Access Control Lists, within CRXDE Lite .
The add and modify privileges can also be administered in CRXDE Lite, or using the User Management console.
For example, the definition of the remove privileges for a group content-authors-no-delete :