Locking a Runbook or Subflow

Lock a runbookClosed An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. or subflow to prevent editing and deletion, for example to protect a production copy. Locking works alongside the existing user permissions that govern who can view or edit automations. It applies to a single runbook or subflow, separate from those permissions.

Note: Locking is not a replacement for user permissions. Permissions control what a user is allowed to do across automations. The lock setting applies to a single runbook or subflow and indicates that the specific automation should not be changed.

What locking allows

The lock state changes which actions are available for a runbook or subflow.

  • Locked: The runbook or subflow is available for viewing, export, and duplication.

  • Unlocked: The runbook or subflow is available for editing, export, duplication, and deletion.

When a runbook or subflow is locked, a lock icon appears next to its name in the list, and the editing and deletion actions are unavailable until you unlock it.

Change the lock state

You set the lock state from the Locked column on the Runbooks page. The same column is available for subflows.

To lock or unlock a runbook or subflow:

  1. Open the Runbooks page for the runbook or subflow type you want to work with.

  2. Find the runbook or subflow in the list, then locate the Locked column.

  3. Click the toggle in the Locked column to switch it on to lock, or off to unlock.

  4. Confirm the change when Riverbed IQ Ops prompts you. The prompt asks you to confirm that you want to lock, or unlock, the selected runbook.

Note: If another user changes the same runbook while you are working, Riverbed IQ Ops reports that the runbook was modified and asks you to refresh the runbook list before you change the lock setting. Refresh the list, then set the lock state again.

Who can change the lock state

Changing the lock state requires the automation permission that governs the lock setting. If your account does not have that permission, the toggle in the Locked column is present but not selectable.

The toggle is also unavailable for built-in runbooks and subflows that are provided by Riverbed IQ Ops.

How the lock affects the Actions menu

The lock state controls which items appear in the ... Actions menu for a runbook or subflow. For details on each action, see Runbooks.

  • While locked, the menu offers the actions that do not change the automation, such as export and duplication. The edit and delete actions are unavailable.

  • After you unlock the runbook or subflow, the edit and delete actions become available again.