OpenMake Meister

Managing Public Workflow Privileges

Public Workflow access privilege is managed at both the "Public" level and the individual "Private" Workflow level.  You can assign a Group access to all Public Workflows by selecting the different access levels at the Public level.   You can further define the access to Public Workflows by assigning a Group access to only specific Public Workflows; for example, you could assign a Group "Read" only access to all Public Workflows by de-selecting "Write", "Execute", and "Delete" at the Public level. You could further define the Group privileges by expanding the "Public" tree and assigning the Group Execute and Delete access to specific Public Workflows.

When defining Public Workflow Privilege for a Group, remember that a new Group is by default granted full access to all Public Workflows, until specifically denied access.  This arrangement means that if you do not customize the Group Privilege, the Group will automatically be given "Administrative" access to all Public Workflows.

Note:  Any User can create or "Add" a Public Workflow. A Public Workflow is created when a User "promotes" a Private Workflow to a Public Workflow.  The creator of a Public Workflow always has full Read, Write, Delete, and Execute access to the Public Workflow.  The creator of a Public Workflow is the only individual who can "demote" that Public Workflow from Public to Private.  Any User belonging to a Group that has Public Workflow access privileges defined at the Public level will automatically have access to any new Public Workflow.  If a Group is only provided access to certain Public Workflows, the Administrator must specifically "grant" the Group access to any new Public Workflows.