Assessment escalations
Escalations ensure that an assessment can only be passed by specific people.
The escalation process
The escalation process for an assessment is as follows:
The workflow escalates the assessment to one or more teams. The assessment status becomes Waiting on escalations.
A member of each escalation team provides their approval or rejection.
When all escalation teams have given their approval, the assessment can be passed manually. If one or more escalation teams have rejected the assessment, the assessment can only be failed, which must be done manually.
A user can only approve one escalation. If two approvals are required from the same escalation team, another member of the team must provide the second approval. Equally, if the same user is a member of multiple escalation teams, the user can only approve the assessment on behalf of one of the escalation teams.
It is not possible to escalate an assessment manually; it can only be done via its workflow.
If you only want one person to be able to pass assessments, create a team with just that user and make this the escalation team.
Escalations that are no longer required
Sometimes an escalation decision may no longer be required.
For example, take a workflow that escalates all high-risk assessments. If an assessment's risk level is assessed as high risk, then later re-assessed to be low risk, the escalation decision is no longer required.
Any escalation decisions that are not required are displayed in a section called Show no longer required escalations.
