Manage workflows

You can use workflows to automate the transition between defined activities for components that exist in a project and for participants that are assigned to the workflow. Users with permissions can start a workflow from a project and participants with an assigned task in the workflow can complete their workflow assignment from a project.

Consider the following guidelines for managing a workflow.
  • A workflow can only start from a project.
  • A component must be in the project to be in a workflow.
  • A participant must be assigned to a project to participate in the workflow for that project.
  • A component can only be in ore than one workflow. If it is, you see a warning that the component is in an active assignment or workflow. You can choose to create the workflow anyway or cancel.
  • Only canceled or completed workflows can be removed from a project.
  • All review workflow must be removed before you can delete the associated project.

Required permissions

To create, view, update, and delete workflows you must either be an Administrator, the project Owner, or have the following permissions:

  • A Seat Type of Standard. If the user has a Seat Type of ReviewOnly or Support, they cannot be given permissions to start a workflow. Administrators can see a user's seat type in the Security module on the User Management tab. Refer to the topic: Things you do on the User Management tab.
  • Create, read, update, and delete permissions to the Projects module.
  • For the Projects module, your user account must be listed under the following Property: can_initiate_assignment.

To work with Review workflows, you also need:

  • Create, read, update, and delete permissions to the Reviews module.

To remove or update a workflow, the project must be active. If you cannot access an option in the steps, make sure the project is active. Follow the steps in: Make a completed project active.