<?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: ACL on Workflows in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/acl-on-workflows/m-p/50462#M29290</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is certainly possible; it is not trivial.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can add an appropriate permission and roles and assign these to groups or people overall or in some node context - just like&amp;nbsp; Read for example.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This will require some changes to the permission model - a new permission and new roles, and possible a new global permission assignment. You woud also need to add permission protection for the WorkflowService ala public-service-security-context.xml. The UI would then need suitable evaluators adding so start workflow is only shown to the appropriate users.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You could limit access directly by groups in a similar way. The evaluator in the UI would be more of a pain; I can not recall if the API allows you to query if the current user is a member of a given group.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;See&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://wiki.alfresco.com/wiki/Security_and_Authentication#Security_Enforcement" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/wiki/Security_and_Authentication#Security_Enforcement&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 12 Mar 2007 15:43:26 GMT</pubDate>
    <dc:creator>andy</dc:creator>
    <dc:date>2007-03-12T15:43:26Z</dc:date>
    <item>
      <title>ACL on Workflows</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/acl-on-workflows/m-p/50461#M29289</link>
      <description>Good day everyone,simple question: is there a way to limit the users who can start a particular workflow? Something like "users form grp1 can start this workflow, users from grp2 can not".Thanks in advance</description>
      <pubDate>Mon, 12 Mar 2007 11:13:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/acl-on-workflows/m-p/50461#M29289</guid>
      <dc:creator>blackout</dc:creator>
      <dc:date>2007-03-12T11:13:10Z</dc:date>
    </item>
    <item>
      <title>Re: ACL on Workflows</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/acl-on-workflows/m-p/50462#M29290</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is certainly possible; it is not trivial.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can add an appropriate permission and roles and assign these to groups or people overall or in some node context - just like&amp;nbsp; Read for example.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This will require some changes to the permission model - a new permission and new roles, and possible a new global permission assignment. You woud also need to add permission protection for the WorkflowService ala public-service-security-context.xml. The UI would then need suitable evaluators adding so start workflow is only shown to the appropriate users.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You could limit access directly by groups in a similar way. The evaluator in the UI would be more of a pain; I can not recall if the API allows you to query if the current user is a member of a given group.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;See&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://wiki.alfresco.com/wiki/Security_and_Authentication#Security_Enforcement" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/wiki/Security_and_Authentication#Security_Enforcement&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Mar 2007 15:43:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/acl-on-workflows/m-p/50462#M29290</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2007-03-12T15:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: ACL on Workflows</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/acl-on-workflows/m-p/50463#M29291</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Andy,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My company is willing to take on this development as part of our project's requirements.&amp;nbsp; In addition to limiting who can start a workflow, we want to prevent users from starting two workflows for the same document (Perhaps by preventing workflows from starting on checked out documents).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;A quick search of JIRA didn't turn up anything, but I wanted to make sure that someone wasn't already working this.&amp;nbsp; It seems like a key piece of workflow functionality, particularly if the workflow performs some actions with privileges that exceed those of the initiating user.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If I don't hear anything in a couple of days, I will create an issue and start looking at the problem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Aaron&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Aug 2007 19:16:36 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/acl-on-workflows/m-p/50463#M29291</guid>
      <dc:creator>amdonov</dc:creator>
      <dc:date>2007-08-27T19:16:36Z</dc:date>
    </item>
  </channel>
</rss>

