Skip to main content
Approval templates let you define reusable multi-round approval configurations that can be imported into any ticket. Instead of manually setting up rounds and approvers each time, create a template once and apply it across tickets for consistent approval workflows.

​
Create a template

1

Navigate to settings

Go to Settings > Approval Templates in your workspace.
2

Create a new template

Click New Template to open the template form.
3

Configure template details

Fill in the template information:
  • Name: A clear, descriptive name (for example, “Finance team approval” or “Security access review”)
  • Description: Explain when this template should be used
  • Workspaces: Select which workspaces can use this template. Leave empty to make it available in all workspaces.
4

Add approval rounds

Configure one or more approval rounds. For each round, set:
  • Policy: Select Any can approve or All must approve
  • Approvers: Select users or who should approve this round
  • Skip conditions (optional): Attach a ticket condition filter that determines whether the round runs. If the conditions do not match at the time the template is applied, the round is skipped instead of requesting approval. See Skip conditions below.
To have rounds run in parallel, drag one round onto another to group them into a single stage. See approval rounds for how stages work.
5

Save the template

Click Save to create the template. It becomes available for import on tickets in the selected workspaces.

​
Apply a template to a ticket

1

Open the ticket

Navigate to the ticket that needs approval.
2

Import the template

In the Approvals section, click the import button and select a template from the list.
3

Confirm import

The template’s rounds and approvers are applied to the ticket. The first round activates immediately and approvers are notified.
Importing a template replaces any existing approval rounds on the ticket. Make sure you want to overwrite the current approval configuration before importing.

​
Skip conditions

Each template round can carry a set of skip conditions built from ticket fields. When the template is applied to a ticket, Ravenna evaluates the round’s conditions against that ticket. If the conditions match, the round is marked Skipped instead of activating, and the approval process continues with the next round.Use skip conditions when a single template needs to cover branching approval flows. For example, a purchase template can include a Finance sign-off round with the condition amount > $5,000 — tickets under that threshold skip the Finance round automatically, while tickets over it still require the extra approval.
1

Open the round

In the template form, expand the round you want to make conditional.
2

Add skip condition sets

Click Add skip condition set and pick a ticket field, an operator, and a value. Add more conditions to require multiple matches, or add another set to skip when any set matches.
3

Save the template

Save the template. The next time it is applied to a ticket, each round’s conditions are evaluated against that ticket and matching rounds are skipped.
Skip conditions are evaluated once, when the template is applied. Changing the ticket after the round is created does not retroactively skip or unskip it.
A round with no skip conditions always runs, matching the previous behavior. If every round in a template is skipped for a given ticket, the ticket’s approval status is set to Approved automatically.

​
Dynamic approvers

Templates support role-based approvers that are resolved dynamically when the template is applied to a ticket. Instead of hard-coding specific users, you can assign approval responsibilities based on the ticket’s context.

Ticket requester

Resolves to the person who submitted the ticket. Useful for self-approval steps or acknowledgment rounds.
Resolves to the requester’s manager. When the template is applied, Ravenna cascades through every configured source in order and uses the first one that returns a manager for the requester:
  1. App-scoped integration — if the ticket targets an application linked to a specific integration, that integration’s manager hierarchy is checked first.
  2. Organization-wide HRIS — if the app source has no manager link (or there is no app-scoped integration), Ravenna falls back to the workspace’s HRIS.
  3. Identity provider — if HRIS has no manager either, Ravenna falls back to the workspace’s identity provider (access provider).
Every source is tried before the role is considered unresolved, so a missing link in one source does not leave the round empty when another source knows the manager. Common for manager-approval workflows where the requester’s direct manager must sign off.
Resolves strictly two levels up the manager hierarchy: requester → manager → manager’s manager. Ravenna first resolves the requester’s direct manager using the same cascade as Requester’s manager (app-scoped integration, then organization-wide HRIS, then the identity provider), and then applies the same cascade again to resolve that manager’s manager.Skip-level resolution is deliberately strict about who counts as the approver:
  • If the requester has no direct manager in any source, the skip-level role has nobody to escalate from and is unresolved.
  • If the direct manager resolves but that manager has no manager of their own in any source, the skip-level role is again unresolved. Ravenna does not fall back to the direct manager.
Use this role for second-level sign-off (for example, a VP or department head reviewing after a direct manager) where routing to the direct manager would defeat the purpose of the escalation.
Dynamic approvers are resolved at the moment the template is applied. If a role cannot be resolved from any of its sources, the approver slot is normally skipped. Requester’s manager and Requester’s skip-level manager are the exceptions: when either role would resolve to nobody, Ravenna substitutes the ticket’s workspace admins as the approvers for that slot so the round is never left without an approver. The skip-level fallback still respects the two-level rule during resolution itself — Ravenna never substitutes the direct manager for a missing skip-level manager.

​
Manage templates

​
Edit a template

Open a template from Settings > Approval Templates and modify its name, description, workspaces, or rounds. Changes only affect future imports. Tickets that already used the template keep their existing rounds.

​
Delete a template

Delete templates you no longer need from the template list. Deleting a template does not affect tickets that previously imported it.

​
Template examples

Manager approval

A single-round template for basic manager sign-off.
A two-round template for purchase or budget requests.
A three-round template for sensitive access requests.
Last modified on August 14, 2026