Documentation for ACL permissions in CMS

Hello akienzle,

See below for list of permissions.

browse,
The user can read metadata property values, but not the associated content. This is the minimal permission required for all other permissions.

read_content,
The user can read the associated content, but not update it.

relate,
This is currently defined but not used.

lock,
The user can check out and cancel check out on an object.

write,
The user can update the metadata of the object.

write_content,
The user can modify the content (or renditions) associated with the object.

delete,
The user can delete the object.

change_permission,
The user can grant/revoke permissions on the object. Changing permissions on the object results in the creation of internal permission.

change_owner,
The user can change the owner of the object.

change_location,
The user can change the parent folder of the object and effectively move the object. This applies to the primary link.

change_folder_links,
The user can link or unlink (primary or symbolic) an object from/to a folder. Being able to link allows to create new or move objects to the folder. The ability to unlink is required to move an object out of the folder.

create_link,
The user can create a symbolic link on the parent folder. The parent must have a change_folder_links permit.

delete_link,
The user can delete the symbolic links from the parent folder. The parent must have a change_folder_links permit.

add_member,
The user can add a member to a group.

delete_member,
The user can delete a member of a group.

show_members,
The user can see members in a group.

apply_policy,
The user can apply/attach retention policy to CMS object.

remove_policy,
The user can remove/detach retention policy from CMS object

apply_hold,
The user can apply retention hold to CMS object

remove_hold,
The user can remove retention hold from CMS object

version,
The user can check in a new version of an object.