---
schema_version: "1"
id: 662fbf98290556f753d96e948d727412fd9f62cb79776e99c54dd7c023b5726d
title: Lock a Blueprint’s Workflows to Prevent Run-Time Changes in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_blueprints_lock_workflow.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_lock_workflow.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9071ff76779507ce14503fe3f88ad003f74a476f6406211f129d09e0ac8905ab
description: Lock workflows from a blueprint to prevent run-time owners from modifying stages or approval criteria after you start the workflow in Agentforce Operations.
products:
  - Cross Cloud
release: "264"
---
# Lock a Blueprint’s Workflows to Prevent Run-Time Changes in Agentforce Operations

Lock workflows from a blueprint to prevent run-time owners from modifying stages or approval criteria after you start the workflow in Agentforce Operations.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d10926e39">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d10926e39 ">
              <p>This feature is a workspace that’s external to your Salesforce org and requires
                an Agentforce Operations license. </p>
              <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                executive.</p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d10926e73">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d10926e73 ">To lock a blueprint's workflows in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d10926e73 ">Admin role, Creator role, or Edit access on the blueprint</td>

          </tr>
        </tbody>
      </table>

Lock workflows that run from a blueprint to enforce process integrity. When you lock workflows, run-time owners can't delete or edit workflows. Locking a workflow locks the workflow’s approval tasks, and the workflow owner can’t approve or reject the task. Use locked workflows for regulated processes, audit-sensitive operations, or any process where consistency across all runs is critical.

1. In the navigation sidebar, click **Blueprints**.
2. Locate the draft blueprint and click **Edit**.
3. Go to the **Settings** tab.
4. For Lock workflows, select **On**.
5. Save and publish the blueprint. Workflows you start from this blueprint are locked. Run-time owners can't modify stages or approval criteria.
    
    If the blueprint includes AI agent tasks, each task must have a saved plan before you can publish. See [Get AI Agent Tasks Ready for Run Time in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_ai_agent_get_ready.htm&release=264.0.0&type=5 "Before you publish a blueprint, make sure that your AI agent tasks are tested and producing reliable results. This section walks you through how plans work, how to test them, and how to lock them for consistent run-time behavior in Agentforce Operations.").

To learn more, see [What You Can and Can't Do in Locked Workflows](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_lock_restrictions.htm&release=264.0.0&type=5 "Understand which actions are permitted or restricted in locked workflows in Agentforce Operations.")