You can create an approval process and attach it to an object to make sure that designated users review certain changes before the object progresses.
This is available for the following types of objects in Adobe Workfront:
For instructions on creating an approval process, see Create an approval process for work items.
This article contains general information about approval processes associated with work items.
If you are an Adobe Workfront administrator, or a user with administrative access to approval processes, you can create the following approval processes for projects, tasks, and issues:
A system-level global approval process: Users can attach these to any of the following:
A group-level global approval process: Users can attach these to the following:
For information about creating system-level or group-level approval process, see Create an approval process for work items.
A single-use approval process: For use with a single project, task, issue, template, or template task. This type of approval process affects only the object that is associated with it and is not available to be associated with any other objects.
For information about creating a single-use approval process, see Associate a new or existing approval process with work.
This article uses the term “global approval process” to differentiate from “single-use approval process.” A global approval process can be used repeatedly.
The term “group-level global approval process” refers to an approval process that can be used repeatedly for items and with statuses associated only with a specific group.
For information about creating a system-level approval process or a group-level approval process see Create an approval process for work items.
You must create the project, task, issue, template, or template task before the approval process can be associated with them.
An approval process is always associated with two essential things:
Each approval process corresponds to a certain work item status in the Workfront system. When you change the status of a work item, an attached approval for that status requires the status change to be confirmed before the new status can be assigned to the item.
You cannot change the status of an item using an approval process to a status other than the one associated with the approval process.
For example, if you have a task approval associated with the status of In Progress, the task automatically changes its status to In Progress when the approval is granted. It cannot automatically change its status to Completed or any other status that is not associated with the approval.
The entities associated with an approval process can be users, job roles, or teams. Users are ultimately responsible for accepting or rejecting the approval. You can assign approvals to users who fulfill a certain role on the project. For example, you can assign an approval to a Project Owner, or Sponsor. For more information, see Create an approval process for work items.
The following scenarios exist:
When you assign an approval to job roles, any user on the Project Team who is associated with the job role can make a decision on the approval. The role associated with the approval can be either their Primary Role or any Other Roles.
For information about the Project Team, see Project Team overview.
When you assign an approval to a team, any member of that team can make a decision on the approval. The team associated with the approval can be either their Home Team or any of their Other Teams.
For information about a user’s roles and teams, see Edit a user’s profile.
When you create a work item, it does not automatically have an approval process attached. You must attach one manually if you want to use one. For information about attaching an approval process to an item, see Associate a new or existing approval process with work.
The Workfront administrator or a user with administrative access to approval processes can create a system-level global approval processes for use throughout the system. A group administrator with administrative access to approval processes can create a group-level global approval process for use only by a certain group that they manage.
If you don’t want to use a predefined system-level or group-level global approval process for a work item, you can create and attach a single-use approval process to it when you have Manage permissions to the object for which you want to attach the approval process.
You can use a single-use approval process only once for the specific item for which it was created. You can associate global statuses as well as group-level statuses for single-use approval processes for projects, tasks, issues, templates, and template tasks.
When attaching a group-level approval process to an item using group-level custom statuses, changing the Group of the project might create a conflict between the approval statuses of the previous group and those existing at the system level. Consider removing the group-level approval processes on the project, or its tasks or issues before updating the group. For information about creating group-level approval processes, see Group-level approval processes. For information about creating custom group statuses, see Create or edit a group status. For information about updating the Group of a project, see Edit projects.
This section explains the following about approving work items:
Attaching a status to an approval process ensures that the item moves through departments in the right order.
Example: You could attach an approval process to the Marketing Department status that requires approval by the Finance department. Then, when someone changes the status for a work item to “Marketing Department,” the item can’t move to that department until the Finance department signs off on it.
For more information about statuses for work items, see the following articles:
The following scenario illustrates how an approval process helps users approve work as a Workfront object progresses through a workflow of several steps in this order:
The Workfront administrator or a user with administrative access to Approval Processes creates an approval process for a project, task, or issue.
You can attach project approval processes to a template, and task approval processes to a template task. After you do this, when someone uses the template to create a project, the approval process becomes a project or task approval process respectively. A single-use approval process attached to a template or template task remains a single-use approval process for projects and tasks.
A user with Manage permission to the project, task or issue attaches the approval process to the item, or creates a single-use approval for the item.
A user assigned to the work item changes its status to the status that initiates the approval process and the approval process begins. (The person who created the approval process defined the relationship between the status and the approval process.)
The designated approvers receive a notification about the pending approval process and they review the work item.
The approval process ends after the designated approvers approve all steps of the process. Or, if they reject a step, the status is either reset to a predefined status, or an issue is created. (The person who created the approval process defined which of these automated steps happens after a rejection.)
Example: An advertising team has created a status called Ready for Printing and an approval process called Designer/ Copywriter Signoff that they associated with this status. This approval process is configured to:
A brochure project owner attaches the Designer/ Copywriter Signoff approval process to the brochure project.
When someone on the project changes the status to Ready for Printing, the copywriter and designer receive notifications asking them to approve or reject it. During the approval process, when they are deliberating whether to approve it or not, the status of the projects displays as Ready for Printing - Pending Approval.
After they both approve the brochure in Workfront, the project status changes to Ready for Printing.
Document approvals are used for a more general approval. Feedback is captured in chat format on the Updates tab. You can use the approval buttons to approve, reject, or approve with changes.
To add approvers to a document after it’s been uploaded to Workfront, see Request document approvals.
Proof approvals are used for a deeper review and generally include more complicated workflows. Feedback is captured with markup tools in the proofing viewer. You can use the approval buttons to approve, reject, or approve with changes.
To add an Automated Workflow to a document proof and designate certain users in the workflow as approvers of the proof, see Create an advanced proof with an Automated workflow.
As a Workfront administrator, you can configure global settings for work-item approval processes in your system. These settings determine various rules for approval processes, like how long an approval decision should be allowed to stay open or how you manage approval delegation in your system. For more information about approval process settings, see Configure global approval settings.