You may require internal sign-off before certain actions can proceed on the platform. This sign-off process is called an approval.
YunoJuno supports approval workflows for two types of events:
Approvals are entirely optional and configured for your organisation. If you do not use approval workflows, contracts can be offered directly and spend requisitions proceed without requiring sign-off.
When you have spend requisition approval configured, a submitted spend requisition must be approved before it can be linked to job posts or contracts. The approver reviews the details of the request and either approves or rejects it.
When you have contract offer approval configured, a hirer cannot send a contract to a contractor until one or more internal approvers have signed off on it. The approval happens while the contract is still in draft — the contractor is not notified and cannot see the contract until the approval is complete and the offer is sent.
Only one approval process can be active for a contract at a time.
You configure one or more approval routes per event type. An approval route defines who needs to approve and how they are selected. There are four types:
You may configure multiple routes for the same event type, allowing hirers to select the appropriate route when submitting for approval — for example, routing to different teams depending on the nature of the work.
When a hirer submits a contract or spend requisition for approval, they select an approval route. The platform then creates an approval request and sends it to the first approver (or group of approvers) in the chain.
An approval request can require one approver or many, in sequence. Each step in the chain is sent to its approver only after the previous step is approved — approvers are notified one group at a time, in order.
At any point there is exactly one step awaiting action. Once that step is approved, the next one is triggered automatically.
Approved — All steps in the chain were approved. The contract can now be offered to the contractor, or the spend requisition can proceed.
Rejected — One step was rejected. The hirer who submitted the request is notified and must decide whether to edit the contract or spend requisition and resubmit.
When a hirer resubmits after rejection, the old approval request is retired and a new one begins from the start. The full history of previous approval attempts is preserved for audit purposes.
If a hirer needs to change the approval route while an approval is already in progress — for example, to route to a different team — the current approval is retired and a fresh one begins with the newly selected route. Any approvers on the old route are notified that it has been cancelled.
It is possible to configure a read-only notification in an approval group. This is useful when you wish to receive a notification that an approval stage has been triggered without having the ability to make an approval decision.
Each approval request moves through the following states:
Within a multi-step approval chain, each step has its own state:
An approver who needs to temporarily hand over their approval duties can create an approval delegation. This covers their approval responsibilities for a defined period without requiring them to reassign their role permanently.
When an approver sets up a delegation, they specify:
During the active window, the designated colleague receives approval notifications and can action pending approvals on the delegator’s behalf.
Any approvals already in progress when the delegation is created are immediately shared with the delegatee — they do not need to wait for new approvals to be submitted.
When a contract offer approval completes successfully, the contract is unblocked and the hirer can send the offer to the contractor. The contractor is then notified and can accept or decline as normal.
If the approval is rejected, the contract remains in draft. The hirer receives a notification explaining the rejection and can edit the contract before resubmitting for approval.
When a spend requisition approval completes successfully, the request is approved and can be linked to contracts.
If the approval is rejected, the hirer is notified and can edit and resubmit the request.