<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Rules and user permissions in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/rules-and-user-permissions/m-p/263387#M216517</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;the rule is not the part that needs changing, it's the action / script / permissions that need some tuning. User A technically does not need full Contributor permission on folder B, only the permission to add another child node to it. So, giving user A only the permissions Read + AddChildren on folder B suffices for the rules action / script to move the document from folder A to folder B. Additionally, you need to withdraw ownership status of user A on the document to exclude any permissions granted by that, otherwise user A will always be able to do what he wants with the document.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Normally, I would write such an action in Java in order to make use of the broader API there. E.g. I can move the document with Java without having to give user A any special permissions just for this action.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 22 Sep 2012 12:14:20 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2012-09-22T12:14:20Z</dc:date>
    <item>
      <title>Rules and user permissions</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/rules-and-user-permissions/m-p/263386#M216516</link>
      <description>Hello everyone,I am testing the rules in folders and I came across the following problem: Say I use a rule to a folderA for a contributor (userA) to submit a document for review. This rule would move the document to folderB and notify userB (site manager) to review it. In order for the rule to work,</description>
      <pubDate>Sat, 22 Sep 2012 10:30:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/rules-and-user-permissions/m-p/263386#M216516</guid>
      <dc:creator>vassilisx</dc:creator>
      <dc:date>2012-09-22T10:30:46Z</dc:date>
    </item>
    <item>
      <title>Re: Rules and user permissions</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/rules-and-user-permissions/m-p/263387#M216517</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;the rule is not the part that needs changing, it's the action / script / permissions that need some tuning. User A technically does not need full Contributor permission on folder B, only the permission to add another child node to it. So, giving user A only the permissions Read + AddChildren on folder B suffices for the rules action / script to move the document from folder A to folder B. Additionally, you need to withdraw ownership status of user A on the document to exclude any permissions granted by that, otherwise user A will always be able to do what he wants with the document.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Normally, I would write such an action in Java in order to make use of the broader API there. E.g. I can move the document with Java without having to give user A any special permissions just for this action.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Sep 2012 12:14:20 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/rules-and-user-permissions/m-p/263387#M216517</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2012-09-22T12:14:20Z</dc:date>
    </item>
  </channel>
</rss>

