Approving or rejecting a job
How approvers review, edit, approve or reject a job that has been submitted for approval, and what happens to the job afterwards.
How approvers review, edit, approve or reject a job that has been submitted for approval, and what happens to the job afterwards.
When a job is submitted for approval, each approval level is assigned to a group of people. Members of the group review the job and either approve it or reject it. This article covers what the approver sees and does. How workflows are set up is in "Creating approval groups and workflow types", and how to find the jobs waiting on you is in "Finding jobs waiting for your approval".
Who can approve and reject
- A member of the approval group assigned to a level can approve or reject at that level. Group members are System Admin, HR or Member users of your organisation. Agency users can never approve. A group marked Hidden in the approval settings still works for the jobs already using it, and its members can approve at their level.
- A System Admin can approve or reject at any level, even if they are not in the group, for groups that belong to their own organisation.
- HR users can only approve or reject when they are in the group for the level.
In a Cascade workflow, approvals move one level at a time, in order. Only the group at the current level can act, and the next group is asked once the current level has approved. In a Parallel workflow every level's group is asked at once and can act in any order. Only the person who submitted the request, or a System Admin, can withdraw it, which is covered in "The approval workflow".
Reviewing a job
- Open the job from the email link, My approvals or the Jobs list. A Member can open a job in Pending Approval only if they are in a group that is currently being asked to approve it.
- Stay on the Details tab. Until a job is approved and set up, this is the only tab shown.
- A banner at the top shows Pending Approval and the group that is awaiting the decision. In a Cascade workflow it also shows the level, for example "Level 1 of 2".
- Read the job details, then scroll to the bottom to reach the Approval Actions card. The Approval History card sits below it and shows the justification the submitter entered, with the answers in the order your organisation set for the justification form, plus any earlier rounds of approval. On a job brought across from the previous system, an Approval History (Vacancy Filler) card with a Legacy record badge sits below that. It shows the approvals recorded in your previous system, read only and separate from approvals made in Recruit.
The Approval Actions card shows the level, its label and the group it is assigned to. If you are not permitted to act, it says "You are not authorised to approve or reject at this level. Only members of [group] or admins can take action." and shows no Approve or Reject buttons.
Editing a job during approval
Each level of a workflow is set to either Can edit + approve or Approve only. Only members of a group asked to approve, and only when that level is set to Can edit + approve, can change the job while it waits. A System Admin can also edit if admin bypass is switched on for your organisation. For everyone else, the Edit option in the actions menu (the three dots at the top right of the job) reads Edit (blocked during approval) and cannot be selected.
- Open the actions menu and choose Edit.
- Change the job details on the Edit Job page and choose Save changes.
- Go back to the job and approve or reject as normal.
Saving an edit does not approve the job or move it to the next level. You still have to approve. The application form cannot be edited at this stage, because it is set up after approval.
Approving
- In the Approval Actions card, type an optional note in the box marked Comments for approval or denial. It can be up to 2,000 characters.
- Choose Approve.
Your comment is stored in the Approval History. What happens next depends on whether other levels remain:
- If more levels remain in a Cascade workflow, you see "Approved at level 1. Moving to level 2." The job stays in Pending Approval and the group at the next level gets the "Action required" email. The person who submitted the job is not emailed at this point. In a Parallel workflow the other groups were already emailed when the job was submitted, so nobody new is emailed. The job stays in Pending Approval until no level is left waiting.
- If your approval completes the last outstanding level, you see "Job has been fully approved!" The job moves to Pending Setup, ready for its application form, recruitment team, pipeline and publishing choices. The person who submitted it gets an email titled "Job [title] has been approved", which includes your name and comment.
Approval does not publish the job. Publishing is chosen later, in the setup steps.
Rejecting
- Choose Reject in the Approval Actions card. The Reject Job window opens.
- Enter a Rejection Reason. This is required and can be up to 2,000 characters. Leaving it blank shows Reason Required.
- Choose Reject Job.
A rejection at any level ends the whole request, not only that level. Approvals already given at earlier levels do not carry over. The job goes back to Draft and the submitter gets an email titled "Job [title] has been rejected" containing your name and reason. Be specific, because that reason is what they will work from.
The submitter can edit the draft and submit it again. It then starts again at level 1 as a new round. When they open the job, a banner says it was previously rejected and shows the reason, with a View history link to the full record.
What each outcome does to the job
| Outcome | Job status afterwards | Who is emailed |
|---|---|---|
| Approved, more levels remain | Pending Approval | In Cascade, approvers at the next level. In Parallel, nobody new. |
| Approved, nothing left waiting | Pending Setup | The person who submitted the job |
| Rejected at any level | Draft | The person who submitted the job |
| Withdrawn by the submitter | Draft | The approvers being asked |