You can create an approval process that users can attach to a work item (project, task, issue, template, or template task), a document, or a proof. An approval process ensures that designated assignees on the object review certain changes before the object progresses in the system.
This article describes how to create a system-level or group-level global approval processes for work items (project, task, issue, template, or template task).
For information about approvals associated with documents or proofs, see the following articles:
Users can also create single-use approval process for a project, task, issue, template, or template task where they have Manage permissions.
This article uses the term “global approval process” to differentiate from single-use approval process. A global approval process can be used repeatedly.
At the group level, a global approval process is restricted to work items and statuses that belong to the group.
For information about single-use approval processes, see Approval process overview and Associate a new or existing approval process with work.
You must have the following:
|Adobe Workfront plan*||Any|
|Adobe Workfront license*||Plan|
|Access level configurations*||
If you are a Workfront administrator or you have administrative access to approval processes, you can create a system-level approval process, or a group-level approval process for a particular group.
If you are a group administrator, you can create group-level approval processes for groups that you manage.
NOTE: If you still don't have access, ask your Workfront administrator if they set additional restrictions in your access level. For information on how a Workfront administrator can modify your access level, see Create or modify custom access levels.
*To find out what plan, license type, or access you have, contact your Workfront administrator.
Click the Main Menu icon in the upper-right corner of Adobe Workfront, then click Setup .
(Conditional) If you are creating a system-level approval process, click Processes > Approvals in the left panel.
If you are creating a group-level approval process, click Groups , click the name of the group, then click Approvals.
Click the Project Approvals, Task Approvals, or Issue Approvals tab, depending on the type of approval process you want to create.
Click New Approval Process.
Specify the following information in the box that displays:
|Approval process name||Type a descriptive name for the approval process. Users see this name when applying the approval process to an object, as described in Associate a new or existing approval process with work.|
|Description||Type a description of the approval process. This displays in the Approvals section in the Setup area next to the name of the approval process.|
Keep this option enabled if you want other users to be able to attach the approval process to projects, tasks, and issues that they create.
This option is enabled by default.
Marking an approval process as inactive is useful when your organization no longer needs to use it, but you want to preserve historical information about its use.
|This approval process can be used by||
If you want the approval process available for projects, tasks, issues, and templates belonging only to a particular group, start typing the name of the group, then select the name when it appears:
This option is not available for single-use approval processes.
WARNING: When you make changes to the group-specific approval process, the existing approval processes that have already been associated with work items might change. For information about these changes, see How group and approval process changes affect assigned approval processes.
For information about listing and managing your group's approval processes from your group's page, see Group-level approval processes.
For information about administrative access to approval processes, see Grant users administrative access to certain areas.
Configure a path for the approval process using the following options.
A path is where you specify what needs to happen in the approval process. You create stages in a path to indicate who needs to do the approval work and in what order.
Start approval process when the status is set to
Select the status that will trigger the approval process on work items. When someone updates a work item to this status, its approval process begins.
The same status cannot be selected for multiple approval process paths.
The statuses available are based on what is selected under the option This approval can be used by (explained in the table above):
|Stage Name||(Optional) Type a name describing the first stage of the path. If you do not specify a stage name, the default name is Stage 1.|
Begin typing the name of the user, team, or job role that you want to designate as an approver for this stage, then click the name when it appears in the drop-down list. You can add only active users, job roles, and teams.
NOTE: Adding a user, team, or role as an approver does not automatically give them permissions to the object associated with that approval. They receive permissions to the object when the approval step is triggered. Otherwise, the objects must be shared with them before they can make an approval decision.
You can also designate an individual as an approver by specifying the individual's role. For example, you can assign a Project Owner, Project Sponsor, Portfolio Owner, Program Owner, or Manager as an approver. These options automatically appear when you begin typing.
You can repeat this process to add multiple approvers to the stage. A single stage can include a combination of users, teams, and job roles as approvers. There is no limit to the number of approvers you can add to a stage.
When you assign job roles as approvers, all users associated with that job role that are also on the project team can make a decision on the approval.
When you assign a team as an approver, any user in that team can make a decision on the approval.
|Only one decision is required||
(Displays only if you add multiple approvers to the stage) Select this option if any one of the approvers on the stage can approve or reject the work item during this stage. This action allows the work item to leave the stage.
When this option is not selected, all of the identified approvers must approve or reject the stage (in any order) before the item leaves the stage. If any one of the approvers rejects the stage, the process interrupts and starts over so that the required changes can be made. Then the approvers can approve or reject the stage once again.
When a team is designated as an approver, any member of the team can grant or reject a stage.
|(Optional) Add another a stage to the path, using the options explained in the three rows above. You can add as many stages to the path as you need.|
|Choose what happens when the approval is rejected|| |
Select the action you want to take if the work item is rejected at any stage of the path:
(Optional) Click Add path to add another path to the approval process, referring to the list of options in the previous step.
The new path must be associated with another status. The path triggers when the item is updated to show this status. You cannot have two paths for the same status.
Now that the approval process is created, continue with any of the following:
For information about editing an approval process, see Edit an approval process.
When you want to create an approval process for a work item (project, task, or issue), you create the approval process first, then create the work item, and then you and your users can associate the approval process with the work item.
For instructions on associating an approval process with a work item, see Associate a new or existing approval process with work.
Any Workfront user with manage permissions to a project, task, or issue can create single-use approval processes for use only on the object where they are created. For more information, see Associate a new or existing approval process with work.
By default, users who have manage permissions on projects, tasks, and issues can create single-use approval processes on them. For information about adding single-use approval processes to projects, tasks, and issues, see the section Associate a single-use approval process with a project, task, issue, template, or template task in the article Associate a new or existing approval process with work.
Users can also change settings for a global approval processes associated with a work item. These changes affect only the project, task, or issue associated with the system-level approval process. For more information, see the section Modify a global approval process for use on a specific object in the article Associate a new or existing approval process with work).