As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
<!– Rajout d'une permission permettant l'ajout de documents dans un dossier sur lequel, l'utilisateur n'a pas de droit de lecture –> <permissionGroup name="Redacteur" allowFullControl="false" expose="true"> <!– <includePermissionGroup permissionGroup="Read" type="sys:base" /> –> <includePermissionGroup permissionGroup="AddChildren" type="sys:base" /> <includePermissionGroup permissionGroup="Write" type="sys:base" /> <includePermissionGroup permissionGroup="CheckOut" type="cm:lockable" /> </permissionGroup>
<!– ============================================= –> <!– Convenient groupings of low level permissions –> <!– ============================================= –> … <permissionGroup name="CreateNodes" expose="true" allowFullControl="false" />
<!– The permission to create new nodes –> <permission name="CreateChildren" expose="true" > <grantedToGroup permissionGroup="AddChildren" /> <!– Add this line –> <grantedToGroup permissionGroup="CreateNodes" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission>
<!– Custom Role Begin –> <!– A Writer can only create content –> <permissionGroup name="Writer" allowFullControl="false" expose="true" > <includePermissionGroup type="sys:base" permissionGroup="CreateNodes" /> </permissionGroup> <!– Custom Role End –>
<permissionGroup name="Writer" extends="true" expose="true"/>
Sorry, my apologies. You're right, to do that you need write and no-read access to the Pending Approval folder.You will need to create a new role let's call it Writer.In permissionDefinitions.xml you need to do the following:<!– ============================================= –> <!– Convenient groupings of low level permissions –> <!– ============================================= –> … <permissionGroup name="CreateNodes" expose="true" allowFullControl="false" /><!– The permission to create new nodes –> <permission name="CreateChildren" expose="true" > <grantedToGroup permissionGroup="AddChildren" /> <!– Add this line –> <grantedToGroup permissionGroup="CreateNodes" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission><!– Custom Role Begin –> <!– A Writer can only create content –> <permissionGroup name="Writer" allowFullControl="false" expose="true" > <includePermissionGroup type="sys:base" permissionGroup="CreateNodes" /> </permissionGroup> <!– Custom Role End –><permissionGroup name="Writer" extends="true" expose="true"/>Invite Writers to the Pending Approval folder with the Writer role.Hope this helps.–Aladdin
<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE permissions ><!–PUBLIC '-//ALFRECSO//DTD PERMISSIONS//EN' 'permissionSchema.dtd' –><!– Note: the above is commented out as spring does not seem to find the dtd –><!– ============================================ –><!– The base permission model for the repository –><!– ============================================ –><!– The parent permission checks were removed 20/1/2006 –><permissions> <!– Namespaces used in type references –> <namespaces> <namespace uri="http://www.alfresco.org/model/system/1.0" prefix="sys"/> <namespace uri="http://www.alfresco.org/model/content/1.0" prefix="cm"/> </namespaces> <!– –> <!– Permission sets link permissions and groups of permissions to types and aspects –> <!– defined in the model. Permissions defined against a type apply to all objects –> <!– that inherit from that type. Permissions defined against aspects apply to all –> <!– objects or only objects that have the aspect applied. For example, the permission –> <!– to lock an object could apply to any object but the permission to unlock an –> <!– object woujld only apply to objects that have the lockable aspect. –> <!– –> <!– =============================================== –> <!– Base permissions available on all types of node –> <!– =============================================== –> <permissionSet type="sys:base" expose="all" > <!– ================= –> <!– Permission groups –> <!– ================= –> <!– –> <!– Permission groups are convenient groups of permissions. They may be used in –> <!– thier own right or as the effective set of permissions. If an authority has –> <!– all the permissions that make up a permission group they also have that –> <!– permission group even though it has not been explicitly granted. –> <!– –> <!– =========== –> <!– Full access –> <!– =========== –> <!– –> <!– By default this is exposed for all objects unless inherited objects choose to –> <!– expose only selected objects at the object level. –> <!– –> <permissionGroup name="FullControl" expose="true" allowFullControl="true" /> <!– ============================================= –> <!– Convenient groupings of low level permissions –> <!– ============================================= –> <permissionGroup name="Read" expose="true" allowFullControl="false" /> <permissionGroup name="Write" expose="true" allowFullControl="false" /> <permissionGroup name="Delete" expose="true" allowFullControl="false" /> <permissionGroup name="AddChildren" expose="true" allowFullControl="false" /> <!– =========== –> <!– Permissions –> <!– =========== –> <!– The permission to read properties on a node –> <!– –> <!– The properties of a node may ony be read if there is read access to the parent –> <!– node. ReadChildren access to the parent node is recursive for all nodes from –> <!– which the node inherits permissions. Access is required down the permission –> <!– tree at all pioints. –> <!– –> <permission name="ReadProperties" expose="true" > <grantedToGroup permissionGroup="Read" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to read the children of a node –> <!– –> <!– This permission is recursive. It requires the same permission is granted to –> <!– all of the parent nodes from which this node inherits permissions –> <!– –> <permission name="ReadChildren" expose="true" > <grantedToGroup permissionGroup="Read" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to write to the properties of a node –> <!– –> <!– This permission includes adding aspects to a node as they are stored as –> <!– a property. –> <!– –> <permission name="WriteProperties" expose="true" > <grantedToGroup permissionGroup="Write" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to delete a node –> <!– –> <!– A node can only be deleted if there is delete permission on the node, if the –> <!– node is accesible via its parent, and if the node can be deleted from its –> <!– parent. Currently, there is no check that all the children can be deleted. –> <!– This check can be added but requires more work so the UI is not checking this –> <!– permission just to show the delete icon. –> <!– –> <permission name="DeleteNode" expose="true" > <grantedToGroup permissionGroup="Delete" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> <requiredPermission on="parent" name="DeleteChildren" implies="false"/> <requiredPermission on="node" name="DeleteChildren" implies="false"/> –> <!– Remove the recursive check for now for performance –> <!– TODO: have one permission to check for delete on an item and one to check –> <!– child permissions when delete is called on the node service –> <!– <requiredPermission on="children" name="DeleteNode" implies="false"/> –> </permission> <!– The permission to delete children of a node –> <!– –> <!– At the moment this includes both unlink and delete –> <!– –> <permission name="DeleteChildren" expose="true" > <grantedToGroup permissionGroup="Delete" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to create new nodes –> <permission name="CreateChildren" expose="true" > <grantedToGroup permissionGroup="AddChildren" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission> <!– The permission to link nodes –> <permission name="LinkChildren" expose="true" > <grantedToGroup permissionGroup="AddChildren" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to delte associations between nodes (not children) –> <permission name="DeleteAssociations" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to read associations –> <permission name="ReadAssociations" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission> <!– The permission to create associations –> <permission name="CreateAssociations" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission> <!– ==================================================== –> <!– Permissions related to the management of permissions –> <!– ==================================================== –> <!– The permission to read the permissions on a node –> <permission name="ReadPermissions" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to the change the permissions associated with a node –> <permission name="ChangePermissions" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> </permissionSet> <!– ================================================ –> <!– Permissions available to all content and folders –> <!– ================================================ –> <permissionSet type="cm:cmobject" expose="selected"> <!– Kept for backward compatibility - the administrator permission has –> <!– been removed to aviod confusion –> <permissionGroup name="Administrator" allowFullControl="true" expose="false" /> <!– A coordinator can do anything to the object or its childeren unless the –> <!– permissions are set not to inherit or permission is denied. –> <permissionGroup name="Coordinator" allowFullControl="true" expose="true" /> <!– A collaborator can do anything that an editor and a contributor can do –> <permissionGroup name="Collaborator" allowFullControl="false" expose="true"> <includePermissionGroup permissionGroup="Editor" type="cm:cmobject" /> <includePermissionGroup permissionGroup="Contributor" type="cm:cmobject" /> </permissionGroup> <!– A contributor can create content and then they have full permission on what –> <!– they have created - via the permissions assigned to the owner. –> <permissionGroup name="Contributor" allowFullControl="false" expose="true" > <!– Contributor is a consumer who can add content, and then can modify via the –> <!– owner permissions. –> <includePermissionGroup permissionGroup="Consumer" type="cm:cmobject"/> <includePermissionGroup permissionGroup="AddChildren" type="sys:base"/> <!– Check out requires write permissions so this will not apply to all –> <!– documents. –> <includePermissionGroup type="cm:lockable" permissionGroup="CheckOut"/> </permissionGroup> <!– An editor can read and write to the object; they can not create –> <!– new nodes. They can cehck out content into a space to which they have –> <!– create permission. –> <permissionGroup name="Editor" expose="true" allowFullControl="false" > <includePermissionGroup type="cm:cmobject" permissionGroup="Consumer"/> <includePermissionGroup type="sys:base" permissionGroup="Write"/> <includePermissionGroup type="cm:lockable" permissionGroup="CheckOut"/> </permissionGroup> <!– The Consumer permission allows read to everything by default. –> <permissionGroup name="Consumer" allowFullControl="false" expose="true" > <includePermissionGroup permissionGroup="Read" type="sys:base" /> </permissionGroup> </permissionSet> <!– =============================== –> <!– Permissions specific to content –> <!– =============================== –> <permissionSet type="cm:content" expose="selected"> <!– Extend some base permission groups to include permissoins related to content. –> <permissionGroup name="Read" extends="true" expose="false"/> <permissionGroup name="Write" extends="true" expose="false"/> <!– Add an execute permission group. –> <permissionGroup name="Execute" allowFullControl="false" expose="false"/> <!– Content specific low-level permissions. –> <!– The permission to read content. –> <permission name="ReadContent" expose="false"> <grantedToGroup permissionGroup="Read"/> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to write content. –> <permission name="WriteContent" expose="false"> <grantedToGroup permissionGroup="Write" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– Execute permission on content. –> <permission name="ExecuteContent" expose="false"> <grantedToGroup permissionGroup="Execute" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <permissionGroup name="Coordinator" extends="true" expose="true"/> <permissionGroup name="Collaborator" extends="true" expose="true"/> <permissionGroup name="Contributor" extends="true" expose="true"/> <permissionGroup name="Editor" extends="true" expose="true"/> <permissionGroup name="Consumer" extends="true" expose="true"/> </permissionSet> <!– ============================================== –> <!– Permissions associated with the Ownable aspect –> <!– ============================================== –> <permissionSet type="cmwnable" expose="selected"> <!– Permission control to allow ownership of the node to be taken from others –> <permissionGroup name="TakeOwnership" requiresType="false" expose="false"/> <!– The low level permission to control setting the owner of a node –> <permission name="SetOwner" expose="false" requiresType="false"> <grantedToGroup permissionGroup="TakeOwnership" /> <!– require to be able to reach the node and set properties in the node –> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" /> –> <requiredPermission on="node" name="WriteProperties" /> </permission> </permissionSet> <!– =================================================== –> <!– Permission related to lock, check out and check in. –> <!– =================================================== –> <permissionSet type="cm:lockable" expose="selected"> <!– At the moment these permissions are hidden so they do not appear in the list –> <!– of permissions. –> <!– Check Out permission - exposed for all object types –> <permissionGroup name="CheckOut" requiresType="false" expose="false"/> <!– Check In permission - only exposed when the lockable aspect is present –> <permissionGroup name="CheckIn" requiresType="true" expose="false"/> <!– Cancel Check Out permission - only exposed for the lockable aspect is present –> <permissionGroup name="CancelCheckOut" requiresType="true" expose="false"/> <!– Low level lock permission –> <permission name="Lock" requiresType="false" expose="false"> <grantedToGroup permissionGroup="CheckOut" /> <requiredPermission on="node" type="sys:base" name="Write"/> </permission> <!– Low level unlock permission –> <permission name="Unlock" requiresType="true" expose="false"> <grantedToGroup permissionGroup="CheckIn" /> <grantedToGroup permissionGroup="CancelCheckOut" /> </permission> </permissionSet> <!– ================== –> <!– Global permissions –> <!– ================== –> <!– –> <!– Global permissions apply regardless of any particular node context. –> <!– They can not be denied by the permissions set on any node. –> <!– –> <!– Admin can do anything to any ndoe –> <globalPermission permission="FullControl" authority="ROLE_ADMINISTRATOR"/> <!– For now, owners can always see, find and manipulate their stuff –> <globalPermission permission="FullControl" authority="ROLE_OWNER"/> <!– Unlock is granted to the lock owner –> <globalPermission permission="Unlock" authority="ROLE_LOCK_OWNER"/> <!– Check in is granted to the lock owner –> <globalPermission permission="CheckIn" authority="ROLE_LOCK_OWNER"/> <!– Cancel check out is granted to the locak owner –> <globalPermission permission="CancelCheckOut" authority="ROLE_LOCK_OWNER"/> </permissions>
Writer=Writer
Hi,What's missing is the I18N message which you should add to webclient.properties.Just add a line:Writer=WriterRegards,–Aladdin
I have tested the Writer role following the instructions with Tomcat Alfresco 1.3.0. and I have detected a permission problem but only when a content rule is defined in the destination workflow folder.The procedure test is the following:OK case:* A Draft folder exists with unchecked Inherit Parent Space Permissions and User1 with Coordinator role. A simple workflow rule is defined for all items to copy/move (both tested) to Pending approval for Inbound content.* A Pending approval exists with unchecked Inherit Parent Space Permissions, User1 with Writer role and User2 with Coordinator role.1.- User1 adds content to Draft folder2.- User1 accepts approval step and content is copied/moved (both tested) to Pending approval correctlyNOK case:* A Draft folder exists with unchecked Inherit Parent Space Permissions and User1 with Coordinator role. A simple workflow rule is defined for all items to copy/move (both tested) to Pending approval for Inbound content.* A Pending approval exists with unchecked Inherit Parent Space Permissions, User1 with Writer role and User2 with Coordinator role. A content rule is created in this folder, don?t matter what, add aspect, simple workflow, add categorization, etc.1.- User1 adds content to Draft folder2.- User1 accepts approval step and a Permission Denied error is issuedAfter this, if you remove the Pending approval content rule all works correctly again.Any idea ? Thank you.
HiIt is possible to change the permissions required for move (and copy) inconfig\alfresco\public-services-security-context.xml.
1) Add an action that moves regardles of permissions
<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE permissions > <!–PUBLIC '-//ALFRECSO//DTD PERMISSIONS//EN' 'permissionSchema.dtd' –> <!– Note: the above is commented out as spring does not seem to find the dtd –> <!– ============================================ –> <!– The base permission model for the repository –> <!– ============================================ –> <!– The parent permission checks were removed 20/1/2006 –> <permissions> <!– Namespaces used in type references –> <namespaces> <namespace uri="http://www.alfresco.org/model/system/1.0" prefix="sys"/> <namespace uri="http://www.alfresco.org/model/content/1.0" prefix="cm"/> </namespaces> <!– –> <!– Permission sets link permissions and groups of permissions to types and aspects –> <!– defined in the model. Permissions defined against a type apply to all objects –> <!– that inherit from that type. Permissions defined against aspects apply to all –> <!– objects or only objects that have the aspect applied. For example, the permission –> <!– to lock an object could apply to any object but the permission to unlock an –> <!– object woujld only apply to objects that have the lockable aspect. –> <!– –> <!– =============================================== –> <!– Base permissions available on all types of node –> <!– =============================================== –> <permissionSet type="sys:base" expose="all" > <!– ================= –> <!– Permission groups –> <!– ================= –> <!– –> <!– Permission groups are convenient groups of permissions. They may be used in –> <!– thier own right or as the effective set of permissions. If an authority has –> <!– all the permissions that make up a permission group they also have that –> <!– permission group even though it has not been explicitly granted. –> <!– –> <!– =========== –> <!– Full access –> <!– =========== –> <!– –> <!– By default this is exposed for all objects unless inherited objects choose to –> <!– expose only selected objects at the object level. –> <!– –> <permissionGroup name="FullControl" expose="true" allowFullControl="true" /> <!– ============================================= –> <!– Convenient groupings of low level permissions –> <!– ============================================= –> <permissionGroup name="Read" expose="true" allowFullControl="false" /> <permissionGroup name="Write" expose="true" allowFullControl="false" /> <permissionGroup name="Delete" expose="true" allowFullControl="false" /> <permissionGroup name="AddChildren" expose="true" allowFullControl="false" /> <permissionGroup name="Execute" allowFullControl="false" expose="false"/> <permissionGroup name="CreateNodes" expose="true" allowFullControl="false" /> <!– =========== –> <!– Permissions –> <!– =========== –> <!– The permission to read properties on a node –> <!– –> <!– The properties of a node may ony be read if there is read access to the parent –> <!– node. ReadChildren access to the parent node is recursive for all nodes from –> <!– which the node inherits permissions. Access is required down the permission –> <!– tree at all pioints. –> <!– –> <!– The permission to create new nodes –> <permission name="CreateChildren" expose="true" > <grantedToGroup permissionGroup="AddChildren" /> <!– Add this line –> <grantedToGroup permissionGroup="CreateNodes" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission> <permission name="ReadProperties" expose="true" > <grantedToGroup permissionGroup="Read" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to read the children of a node –> <!– –> <!– This permission is recursive. It requires the same permission is granted to –> <!– all of the parent nodes from which this node inherits permissions –> <!– –> <permission name="ReadChildren" expose="true" > <grantedToGroup permissionGroup="Read" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to write to the properties of a node –> <!– –> <!– This permission includes adding aspects to a node as they are stored as –> <!– a property. –> <!– –> <permission name="WriteProperties" expose="true" > <grantedToGroup permissionGroup="Write" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to delete a node –> <!– –> <!– A node can only be deleted if there is delete permission on the node, if the –> <!– node is accesible via its parent, and if the node can be deleted from its –> <!– parent. Currently, there is no check that all the children can be deleted. –> <!– This check can be added but requires more work so the UI is not checking this –> <!– permission just to show the delete icon. –> <!– –> <!– The permission to read content. –> <permission name="ReadContent" expose="false"> <grantedToGroup permissionGroup="Read"/> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to write content. –> <permission name="WriteContent" expose="false"> <grantedToGroup permissionGroup="Write" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– Execute permission on content. –> <permission name="ExecuteContent" expose="false"> <grantedToGroup permissionGroup="Execute" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <permission name="DeleteNode" expose="true" > <grantedToGroup permissionGroup="Delete" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> <requiredPermission on="parent" name="DeleteChildren" implies="false"/> <requiredPermission on="node" name="DeleteChildren" implies="false"/> –> <!– Remove the recursive check for now for performance –> <!– TODO: have one permission to check for delete on an item and one to check –> <!– child permissions when delete is called on the node service –> <!– <requiredPermission on="children" name="DeleteNode" implies="false"/> –> </permission> <!– The permission to delete children of a node –> <!– –> <!– At the moment this includes both unlink and delete –> <!– –> <permission name="DeleteChildren" expose="true" > <grantedToGroup permissionGroup="Delete" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to create new nodes –> <permission name="CreateChildren" expose="true" > <grantedToGroup permissionGroup="AddChildren" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission> <!– The permission to link nodes –> <permission name="LinkChildren" expose="true" > <grantedToGroup permissionGroup="AddChildren" /> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to delte associations between nodes (not children) –> <permission name="DeleteAssociations" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to read associations –> <permission name="ReadAssociations" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission> <!– The permission to create associations –> <permission name="CreateAssociations" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false" /> –> </permission> <!– ==================================================== –> <!– Permissions related to the management of permissions –> <!– ==================================================== –> <!– The permission to read the permissions on a node –> <permission name="ReadPermissions" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> <!– The permission to the change the permissions associated with a node –> <permission name="ChangePermissions" expose="true" > <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" implies="false"/> –> </permission> </permissionSet> <!– ================================================ –> <!– Permissions available to all content and folders –> <!– ================================================ –> <permissionSet type="cm:cmobject" expose="selected"> <!– Kept for backward compatibility - the administrator permission has –> <!– been removed to aviod confusion –> <permissionGroup name="Administrator" allowFullControl="true" expose="false" /> <!– A coordinator can do anything to the object or its childeren unless the –> <!– permissions are set not to inherit or permission is denied. –> <permissionGroup name="Coordinator" allowFullControl="true" expose="true" /> <!– A collaborator can do anything that an editor and a contributor can do –> <permissionGroup name="Collaborator" allowFullControl="false" expose="true"> <includePermissionGroup permissionGroup="Editor" type="cm:cmobject" /> <includePermissionGroup permissionGroup="Contributor" type="cm:cmobject" /> </permissionGroup> <!– A contributor can create content and then they have full permission on what –> <!– they have created - via the permissions assigned to the owner. –> <permissionGroup name="Contributor" allowFullControl="false" expose="true" > <!– Contributor is a consumer who can add content, and then can modify via the –> <!– owner permissions. –> <includePermissionGroup permissionGroup="Consumer" type="cm:cmobject"/> <includePermissionGroup permissionGroup="AddChildren" type="sys:base"/> <!– Check out requires write permissions so this will not apply to all –> <!– documents. –> <includePermissionGroup type="cm:lockable" permissionGroup="CheckOut"/> </permissionGroup> <!– An editor can read and write to the object; they can not create –> <!– new nodes. They can cehck out content into a space to which they have –> <!– create permission. –> <permissionGroup name="Editor" expose="true" allowFullControl="false" > <includePermissionGroup type="cm:cmobject" permissionGroup="Consumer"/> <includePermissionGroup type="sys:base" permissionGroup="Write"/> <includePermissionGroup type="cm:lockable" permissionGroup="CheckOut"/> </permissionGroup> <!– The Consumer permission allows read to everything by default. –> <permissionGroup name="Consumer" allowFullControl="false" expose="true" > <includePermissionGroup permissionGroup="Read" type="sys:base" /> </permissionGroup> <!– Custom Role Begin –> <!– A Writer can only create content –> <permissionGroup name="Writer" allowFullControl="false" expose="true" > <includePermissionGroup type="sys:base" permissionGroup="CreateNodes" /> </permissionGroup> <!– Custom Role End –> </permissionSet> <!– =============================== –> <!– Permissions specific to content –> <!– =============================== –> <permissionSet type="cm:content" expose="selected"> <!– Content specific roles. –> <permissionGroup name="Coordinator" extends="true" expose="true"/> <permissionGroup name="Collaborator" extends="true" expose="true"/> <permissionGroup name="Contributor" extends="true" expose="true"/> <permissionGroup name="Editor" extends="true" expose="true"/> <permissionGroup name="Consumer" extends="true" expose="true"/> <permissionGroup name="Writer" extends="true" expose="true"/> </permissionSet> <!– ============================================== –> <!– Permissions associated with the Ownable aspect –> <!– ============================================== –> <permissionSet type="cm:ownable" expose="selected"> <!– Permission control to allow ownership of the node to be taken from others –> <permissionGroup name="TakeOwnership" requiresType="false" expose="false"/> <!– The low level permission to control setting the owner of a node –> <permission name="SetOwner" expose="false" requiresType="false"> <grantedToGroup permissionGroup="TakeOwnership" /> <!– require to be able to reach the node and set properties in the node –> <!– Commented out parent permission check … <requiredPermission on="parent" name="ReadChildren" /> –> <requiredPermission on="node" name="WriteProperties" /> </permission> </permissionSet> <!– =================================================== –> <!– Permission related to lock, check out and check in. –> <!– =================================================== –> <permissionSet type="cm:lockable" expose="selected"> <!– At the moment these permissions are hidden so they do not appear in the list –> <!– of permissions. –> <!– Check Out permission - exposed for all object types –> <permissionGroup name="CheckOut" requiresType="false" expose="false"/> <!– Check In permission - only exposed when the lockable aspect is present –> <permissionGroup name="CheckIn" requiresType="true" expose="false"/> <!– Cancel Check Out permission - only exposed for the lockable aspect is present –> <permissionGroup name="CancelCheckOut" requiresType="true" expose="false"/> <!– Low level lock permission –> <permission name="Lock" requiresType="false" expose="false"> <grantedToGroup permissionGroup="CheckOut" /> <requiredPermission on="node" type="sys:base" name="Write"/> </permission> <!– Low level unlock permission –> <permission name="Unlock" requiresType="true" expose="false"> <grantedToGroup permissionGroup="CheckIn" /> <grantedToGroup permissionGroup="CancelCheckOut" /> </permission> </permissionSet> <!– ================== –> <!– Global permissions –> <!– ================== –> <!– –> <!– Global permissions apply regardless of any particular node context. –> <!– They can not be denied by the permissions set on any node. –> <!– –> <!– Admin can do anything to any ndoe –> <globalPermission permission="FullControl" authority="ROLE_ADMINISTRATOR"/> <!– For now, owners can always see, find and manipulate their stuff –> <globalPermission permission="FullControl" authority="ROLE_OWNER"/> <!– Unlock is granted to the lock owner –> <globalPermission permission="Unlock" authority="ROLE_LOCK_OWNER"/> <!– Check in is granted to the lock owner –> <globalPermission permission="CheckIn" authority="ROLE_LOCK_OWNER"/> <!– Cancel check out is granted to the locak owner –> <globalPermission permission="CancelCheckOut" authority="ROLE_LOCK_OWNER"/> </permissions>
Hi,What does your rule do?Thanks,–Aladdin
