[
http://www.jahia.net/jira/browse/SENSEI-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Draier resolved SENSEI-57.
---------------------------------
Resolution: Fixed
> NStep Workflow: default roles mapped to ACL not clearly indicated
> -----------------------------------------------------------------
>
> Key: SENSEI-57
> URL: http://www.jahia.net/jira/browse/SENSEI-57
> Project: Jahia Workflows
> Issue Type: Sub-task
> Affects Versions: Workflow 6.0
> Environment: 22951
> Reporter: Stephane Croisier
> Assignee: Thomas Draier
> Priority: Major
> Fix For: Workflow 6.0
>
> Attachments: John_example.jpg,
> John_RWA_can_publish_without_the_role.jpg, screenshot-1.jpg
>
>
> When switching to another Nstep workflow, ACL are currently automatically
> mapped on roles (kind of default values for each step). However there is no
> indication of such "default values" in the Workflow sub-engine. So this does
> not help understand who can exactly make what. for example if I add a user,
> does this automatically remove all the other user who have RW permission on
> the page?
> So it would be clearer if we really use current ACL as default values which
> could then be removed, replaced, restricted to certain users, etc...
> The manager needs to be sure of who can exatly perform which action.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
