The approval workflow

Getting a job signed off before it goes live.

If your organisation requires approvals, every new job needs sign-off before it can be set up and published. This is configured under Settings > Approval Workflows, and happens automatically as part of creating a job.

Submitting a job for approval

When you reach the Approvals step of job creation:

1. Choose the approval workflow that applies (your organisation may have more than one).
2. For each approval level, choose the group who should approve, unless the workflow has already locked a level to a specific group.
3. Fill in any justification fields your organisation requires.
4. If you're an administrator and admin bypass is enabled, you can tick a switch to skip pending approvals and mark the job as approved immediately.

Cascade vs. parallel approval

Workflows run in one of two modes:

• Cascade: approval levels are approved in order, one after another. A later level can't act until the one before it has signed off.
• Parallel: all levels can approve at the same time, independently of each other.

Each level can also be set to allow the approver to edit the job before approving it, rather than only approving as-is.

Approving or rejecting

Approvers act on whichever level is currently open, with an optional comment or reason. Once the final level approves, the job moves to Pending Setup, ready for its application form, team, and pipeline to be configured.

Rejecting a job, or the submitter withdrawing it, sends it back to Draft so it can be adjusted and resubmitted.

Publishing after approval

Approval and publishing are separate decisions. Once a job is approved and through setup, whether it publishes immediately or on a future date is chosen on the Publishing step of setup, not as part of the approval itself.