Workspace-level and Project-level Workflow Assignments

After you have set up a custom workflow with the right context type to replace a default workflow, you must decide whether to replace it at the project level or the workspace level.

Project-level Custom Workflow Assignments

You can assign workflows at the project level to take the place of default system workflows or workflows that exist at the workspace level. There are two ways a workflow can be assigned at the project level. 1) You can assign the workflow directly to objects and actions at the project level, or 2) You can assign the workflow to objects and actions at the workspace level, and then you can have all projects and child workspaces within that workspace inherit the workflow assignment.

Either way, workflow assignments must eventually make it to projects in order to have any effect. So, the easiest and most direct way to assign custom workflows for one project is at the project level.

Workspace-level Custom Workflow Assignments

If you have several projects in a workspace and you want a workflow assignment to take effect for all of the projects in that workspace, then you can assign a workflow at the workspace level. After that, you can have all of the projects in the workspace inherit the workflow assignment.

This is a convenient way to assign workflows for multiple projects at once, but in order for a workspace-level workflow assignment to take effect for a project within the workspace, you need the privileges required to edit that project.