Members of the workspace build its templates. Each step opens in a , so set up the channels your teams work in before you start.
Create a template
1
Open templates
Go to Lifecycles in your workspace’s sidebar, open the Templates tab and click New.
2
Choose a starting point
In Start from, pick an example to adjust, or Blank template to start from a single task.
3
Choose the channels
In Lifecycle channel, choose where each lifecycle’s parent ticket is created. Under Team channels, choose where each team’s steps open, in any workspace, such as a People channel in your HR workspace. Leave a team empty to use the lifecycle channel. Then click Create.
Edit the steps
The Tasks tab lists every step with its Kind, Owner, Unlocks and Depends on. Click Add task to add one, or click a step to open it. A step’s menu has Duplicate and Delete.A step unlocks on its Unlocks day, once every step in Depends on is finished. The Preview tab lays the template out around a sample date, so you can check the order before you publish.Changes save automatically as you edit. The header shows Unsaved changes, Saving… and Saved, or Fix the problems to save when something needs fixing.
Step kinds
Manual steps
The owner does the work and closes the step’s ticket, or clicks Mark done on the step.Form steps
The step’s ticket opens with a form for someone to fill out, and submitting it completes the step. To move past a form nobody will fill, skip the step. You can prefill it and choose who it’s sent to.Learn more about Form steps
Workflow steps
A workflow on the Lifecycle Step runs when the step’s ticket opens, and the step completes when the workflow closes the ticket. The step’s Workflows section lists the workflows set to it:- Create workflow creates one in the workspace where the step’s ticket opens, already set to close the step’s ticket, and turns it on. It’s available once the template is published, to members of that workspace.
- Open workflow replaces it once the step has an active workflow. One workflow runs each step, so add actions to it to do more.
Learn more about lifecycles and workflows
Access steps
In Access, choose what the step does when it unlocks:- Grant an access level: requests the you choose in Access level for the person. Its decides approval, and the step completes when the access is provisioned. Marking the step done, skipping it or cancelling the lifecycle withdraws a request that’s still pending.
- Revoke all the person’s access: revokes every Ravenna manages for the person, then completes the step. Revocations still in progress, or skipped because the person has the access through another entitlement, are listed in a note on the step’s ticket, so check it before you treat the person’s access as gone.
Granting access uses access requests (
sar3), which are on by default. If they’re turned off for your organization, the step shows Needs attention with “Access wasn’t requested”. Contact your Ravenna representative to turn them back on.Template settings
On the Settings tab:Publish
Click Publish to make a new version. Lifecycles you start from now on use it, and running lifecycles keep the version they started on. The header shows Published v2, or v2 · unpublished changes when you’ve edited since.Every Form step needs a form, and every Access step needs an access level or Revoke all the person’s access, before you can publish. A step without one is flagged: choose its Ticket form or its access, or change its Kind.Publishing checks that the workflows running the template’s steps still fit: each step a workflow runs is still a Workflow step in that workflow’s workspace, and every answer the workflow reads is still collected before it. If one doesn’t fit, the step it’s about says how to fix it.From the template menu:- Discard unpublished changes puts the steps back to the published version and keeps the template’s settings.
- Delete stops new lifecycles from starting from the template. Running lifecycles keep going on their version.
Learn more about running lifecycles