In many organizations there are more than one person involved in the approval process. Approval chains represent the order in which approvals are sent and made, and still include single-person approvals.
Here we cover only the approval process.
The approval process starts in any deliverable by clicking an empty checkbox . This will open a modal like the one below.
If you have the rights, you can click approve and the deliverable will be approved. If another approval is needed beyond your own, rather click 'approve and send'. Clicking this button will add the 'Send to' field, where you can select the next approver in the approval sequence. If the sequence is unknown, you should consult your Onboard Guide or other project expert.
This will send an Action Item to the named party for approval. Once clicked they will see a modal for their approval. Similar to the previous step, they can click 'approve' and the deliverable is approved, or they can 'approve and send' to obtain another approval in the sequence.
Note: what has been shown above is a "flexible approval process". Anybody with edit rights can start it, and submit entities for approval. Nonetheless more rigourous organizations might need a structured approach to approvals. This is accomplished via "static workflows" (search for the static workflows section here). In case a static workflow is created for a given deliverable, you won't be able to select to whom send the deliverable for approval: the workflow with all its steps and conditions will be already set.
For any approved deliverable, to view the approvals that took place, click . This will produce a modal like the below:
If you click view steps , you will be shown the steps performed and the timing of each.
If you click entity snapshot you will see a read-only version of the deliverable in its approved state.
The history of all approvals will be shown in the approval chain modal, regardless whether accepted or rejected.