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
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.

​
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.
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 — with one exception: when the Requester’s manager role resolves to nobody across all sources, Ravenna substitutes the ticket’s workspace admins as the approvers for that slot so the round is never left without an approver. This fallback only applies to the Manager role, and only when it would otherwise resolve to no one — other dynamic roles (and mixed rounds where another source already fills the slot) are unaffected.

​
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 July 27, 2026