The Workflow Assignments tab lets you set up approval processes for budget moves, potential change orders, client change orders, and documents. The settings include defining the number of steps in your approval processes and making assignments of who approves each step.
You can set up dollar-value thresholds based on contract type at an organization level for PCOs or CCOs. The organization has an approval matrix where any dollar amount over the threshold set must be approved. Approval for budget moves and document approvals have ordered steps assigned to roles.
Add a workflow assignment threshold to set the amount at which a PCO or CCO must be approved.
The workflow steps set at the organization level are performed after those set at the PCO/CCO and project levels. However, if the value of the PCO or CCO is below the organization level thresholds, the workflow thresholds set at the organization level will not show in the Workflow Assignments.
Thresholds are absolute values, so a pricing change in either direction starts the approval workflow.
Go to the Workflow Assignments tab.
Select the PCO approval setup or CCO approval setup tab.
Click the Add approval icon.
In the Add approval slide-out panel, enter the threshold amount and approval step title.
Indicate whether projects must select specific users based on assigned roles. When the check box is selected, the project must add a user who has that role to that step before workflow can be started. If the check box is not selected, all users in that role are eligible for approval.
Enter the roles for the Assign approval roles.
Click Add to complete.
If you want the approval workflow for the threshold to have additional steps, click Add another step. To change the position of a step, select it, and then use the up and down arrows to the right of the steps to move up or down.
Organization-level thresholds cascade to every PCO or CCO. You can add additional steps at the project level, which are performed before the steps set at the organization level. You can add additional approval steps at the individual PCO or CCO level, which, regardless of the value of the PCO or CCO, are always first.
Add a budget move approval workflow when you want the budget move to be approved before being sent as a draft to InEight Control.
When there is a workflow in place, the budget move is not sent to Control until it has been approved in Change.
From the organization Settings > Workflow assignments tab, select the Budget move approval setup subtab.
Click the Add approval icon. The Add approval slide-out panel opens.
Enter the step title and the approver roles.
Indicate whether projects must select specific users based on assigned roles. When the check box is selected, the project must add a user who has that role to that step before workflow can be started. If the check box is not selected, all users in that role are eligible for approval.
Click Add.
Repeat steps 2-5 for each step you want to add.
Click Save.
You can add steps at the project level.
When changes to roles in the project team occur, such as changing responsibilities or filling in for another user, updates to a workflow that is already in progress can happen. Approval workflows that are already in progress retain the approval assignments that were in place when the workflow initiated. Changes made to the workflow configuration after an item enters the approval process do not automatically update or reassign existing workflow assignments.
When a workflow step is assigned to a role, and the original user is removed from that role while another user is added to it, the new user inherits access to the approval workflow that is in progress. This is because the workflow is tied to the role assignment, not the individual user. As a result, the workflow item is shown in the new user's Action Items list.
The new user does not receive an email for approval but is able to view the items on the Action Items list and within the individual item.
When the approval workflow configuration is changed from a role assignment to a named-user assignment after the workflow has started, the existing approval workflow assignments in progress do not automatically switch to the new assignment model. Those workflow assignments continue to reference the original role assignment and are only visible to users who currently hold that role. You can add the newly named user approver to the original workflow role so that pending approval items show in their Action Items list. After all pending workflows are completed, you can remove the user from the role and maintain the workflow as a named-user assignment.
Any workflow items initiated after the project settings are updated from a role assignment to a named-user assignment use the new named-user configuration and route approvals accordingly.
Additional Information
9977 N 90th Street, Suite 250 Scottsdale, AZ 85258 | 1-800-637-7496
© 2026 InEight, Inc. All Rights Reserved | Privacy Statement | Terms of Service | Cookie Policy | Do not sell/share my information
