Guide
Guide
A request that moves from one approver to the next, in order, with a response deadline and a different chain depending on who asks.
The room manager first, then the head office. In an institution, a booking request often follows a hierarchy. Multi-level approval mirrors that workflow: each level is only asked once the previous one has agreed, a refusal ends the request wherever it happens, and an unanswered request expires instead of blocking the slot forever.
Multi-level approval builds on booking validation: enable it on the resource first, with its approvers. If it is new to you, the guide "Set up booking validation" walks you through it.
Tick "Multi-level approval". Then set the response deadline, in hours per level: past that time without a decision, the request is refused and the slot freed. Leave it empty to let a request wait indefinitely.
Back on the resource, assign a level to each approver. The request goes from level 1 to level 2, and so on. Within a level, the first to answer decides: put several people there to cover absences.
A per-group chain replaces the default chain for members of that group. Teachers can thus have a single level while students have two. A chain without approvers is ignored.
The requester sees the progress — "level 1 of 2" — on their booking and in their emails. Each approver is only notified when it is their turn and decides from the dashboard or the link in the message. The full trail of every approval appears in the statistics export.