Roles and permissions
The following users can configure approvals:
Task approvals - Anyone with manager or contributor permissions for an object that supports tasks.
Repeating task approvals - Anyone with manager or contributor permissions for a control, label, or risk
Policy approvals - Anyone with manager permissions for the policy
The approval workflow provides a structured process that ensures completed work is formally reviewed and verified by designated approvers before being finalized. When a record is submitted for approval, Hyperproof creates a series of approvals based on the configured approval workflow for the submitted object.
Approvals on most objects can be created at the same time as the object or added later. Regardless of when the approval is created, the approval options are the same.
Assume that you are at the point in creating or editing an object where you want to configure approvals, and do the following:
Open the object where you want to configure approvals.
In most cases, approvals are under Automations. Click the Automations drop-down.
Make sure the Enable approvals option is turned on.
In the Approval flow type section, select one of the following options:
Note: This option displays only when more than one approval step has been configured.
Sequential - Indicates that the approval steps occur one after another in order. If you have two steps, the approvals for Step 2 aren't created until the approvals for Step 1 are completed.
Parallel - All steps are reviewed simultaneously. If you have two steps, the approvals for both Step 1 and Step 2 are created simultaneously. Having multiple steps lets you set different completion rules for each step.
Click the +Step button to add a step to the approval process.
The Completion rule field defaults to Everyone must approve. You must select at least one approver before you can modify this field.
Everyone must approve - All assigned approvers must mark their decision to complete the step. If all approvers mark their decision as Approved, then the step is considered Approved. If any one person selects Change requested, then the entire step is marked as Change requested.
Minimum approvals required - A user-specified number of approvers must mark their approval as Approved to complete the step.
How many approvals are required? - Enter the number of approvals that must be marked Approved for the step to be completed. This field is required if you have selected Minimum approvals required as the completion rule for this step.
This step ends if any assignee marks their decision as Change requested. If the step ends due to a Change requested decision, any incomplete approval requests are canceled.
In the Approvers drop-down, select one or more approvers. Approvers must be Hyperproof users, not contacts. These users are not required to be members of the target object, such as the Control where you are creating the task. From this list, you can select the following:
Specific Hyperproof users by name. Note that if you select contacts as approvers, they can't complete the approval because they can't log into Hyperproof.
User fields from the task, target, or policy, such as Created by.
Note: If you select duplicate users as approvers when selecting user fields or users by name, Hyperproof automatically detects the duplicates and generates only one approval for the duplicate users.
Continue configuring additional approval steps as needed.
To automatically move the object to the next status when all approvals are completed, toggle on the Auto-<action> <object> when approved option. If this option is toggled off, you must manually move the object to the next status.