Defining Roles for a Workflow

An administrator creates role definitions for use in a workflow.

Workflow roles are not assigned permanently to users or groups. Instead, the participants associated with roles can change from one type of workflow to another, from one instance of a particular workflow to another, and even from one task of a workflow to the next.

We recommend that you create pairs of role definitions for use with workflow, one for an individual user assignment (Task Owner) and one for a pool assignment (Task Audience), such as for a parallel workflow step, or for posting to an audience where any audience member can accept the job. See The Difference Between a Task Audience and a Task Owner. Role definitions that are created for workflow typically do not have any capabilities assigned. This guards against inadvertently granting capabilities to users who participate in a workflow.

If your organization has already implemented workflow for some projects, your repository may contain role definitions that are suitable for a new workflow definition. Be sure to create all of the roles needed for the workflow, including the special roles for Status Changer, Task Owner, and Task Audience. See About Roles in Workflow.

  1. Right-click Role Definitions and select Create > New Role.
    The New Role dialog appears.
  2. Enter a Name for the role.
    The name should clearly identify the role purpose as supporting a workflow, and whether the role is intended for an individual or group assignment.
    For example, use a singular term for the role name for an individual assignment, and a plural term for a group assignment, or include the word Pool in the role name for a group assignment.
  3. Enter a Description for the role.
    The description should indicate the role supports a workflow, is intended for a group assignment, and could indicate no capabilities are assigned in the role.
  4. Do not select capabilities for the General Privileges, Custom Attributes, or Annotations tabs.
  5. Click OK.
The role definition is saved in the repository and can be referenced in Audience Parameters and Task Sequence documents, then used to assign workflow tasks to users or groups.