If an object is moved to a different folder, what will happen to the node’s security permissions?

The Alfresco Content Services security model is fundamentally hierarchical. By default, a node (a file or folder) inherits its Access Control List (ACL) from its parent folder. When a node is moved from one folder to another, its parent in the repository hierarchy changes. Consequently, the node ceases to inherit permissions from its original parent and begins inheriting the ACL from its new parent folder. This ensures that content automatically adopts the security context of the location to which it is moved, which is a core principle of managing permissions within the Alfresco repository.

B. It will inherit the ACL from the user who is moving it.

A user's permissions determine if they can perform the move action, but the object's permissions are derived from its location, not the user acting upon it.

C. It will inherit the system wide ACL.

There is no single "system wide ACL" for content. Permissions are granular and determined by a node's position within the folder hierarchy, not a global setting.

D. It will keep its old ACL.

This is incorrect for the inherited portion of its permissions. While a node can have its own local ACL, it also inherits permissions, and that inherited part will change upon moving.

1. Alfresco Content Services 5.2 Documentation, Administering, Managing Permissions: The documentation states, "By default, a folder or content item inherits the permissions of its parent folder." This core principle dictates that changing the parent by moving the item will change the source of inherited permissions. (Source: Alfresco Content Services 5.2 Documentation, docs.alfresco.com, Section: "Managing permissions").

2. Alfresco Content Services 5.2 Documentation, Repository Concepts, Permissions: This section explains the hierarchical model: "The permission model is hierarchical. Permissions set on a container (a space) are inherited by the objects it contains (other spaces, content items)." A move operation is a change of container, which directly implies a change in inherited permissions. (Source: Alfresco Content Services 5.2 Documentation, docs.alfresco.com, Section: "Repository concepts > Permissions").