Skip to main content
Locking a workflow restricts who can edit it to Admins and Owners only. Once a workflow is locked, other roles can still see it and it keeps running normally—they just can’t modify or delete it. Locking protects the automation your incident response depends on from accidental edits, well-meaning tweaks, and unauthorized changes.

​
Why Lock a Workflow?

Workflows often encode critical, hard-won response logic—who gets paged, which channels get created, how stakeholders are notified. As more people gain access to build and edit workflows, a single accidental change to a load-bearing workflow can quietly break part of your response. Locking the workflows you rely on most keeps them stable while still letting your team build and iterate on everything else.

​
How to lock or unlock a workflow

1

Open the Workflows List

Go to your list of workflows in Rootly.
2

Open the Workflow Menu

On the far right of the workflow you want to protect, select the ellipsis (⋯).
3

Lock or Unlock

Select Lock to restrict edit access to Admins and Owners, or Unlock to restore normal edit access.
You can also lock or unlock a workflow from the ellipsis while editing it. Only Admins and Owners can lock or unlock a workflow.

​
How Do I Know a Workflow Is Locked?

A locked workflow shows a lock icon in the workflow list, so it’s clear at a glance which workflows are protected. Users without Admin or Owner permissions will find the edit and delete controls unavailable on those workflows.

Workflows Overview

The umbrella page — locking is one of the safeguards you apply to a workflow.

Workflow Types

Understand which trigger events and objects a workflow can react to before locking it.

Workflow Conditions

Conditions govern when a workflow runs — worth double-checking before you lock the workflow.