π Web | π€ Yokoy admin with Workflow Designer permissions
π’ Enterprise plan
This template is restricted to Yokoy Enterprise plans. Your company must have this plan to use it to build your own workflow.
You can set up a custom approval flow that includes several Yokoy users who must approve the expense.
It uses Assign approvers with property and All approvers must approve or Final approval nodes. The first node assigns the group of approvers to the expense document, while the second one deals with the any/all approval logic.
Both of these nodes must be used in combination to create an approval group flow.
You can also configure this approval workflow with other approval flows.
Configuring the workflow
To configure the workflow:
Step | Node(s) to use | Options required |
1a | New (status) | Submit action |
1b | Draft (status) | Submit action |
1c | Needs revision (status) | Submit action |
2 | Assign approvers with property (activity) |
|
3 | All approvers must approve (approval) / Final approval (approval)
| You can use either of these approval nodes depending on whether you want to force all approvers to approve (all must approve) or whether a single approver can approve the document and move the document to the next step (final approval). |
4a | Needs revision (status) | Send back action |
4b | Draft (status) | Recall action |
4c | Rejected (status) | Reject action |
4d | In review (status) | No action |
βοΈ Note
Nodes and actions to use after the approval node will depend on the specific scenario. The list given as an example is non-exhaustive.
Remember to always connect an approval node to Need revision, Draft, Reject, and In review statuses.
In the end, the workflow looks like this:

