---
schema_version: "1"
id: 7e3e4f22108a8830e5ad7558b4f6c48979313ce8ac7fb6ec3560114698f8a18f
title: Manage Blueprints 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_manage.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_manage.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 442bb2a5a96c475f9b02c936223a18491bb917e23d0f21525dd038d610129aa1
description: Maintain and evolve your blueprints over time in Agentforce Operations. Learn how versioning works, when to use collaborative editing, and what happens when you delete blueprints.
products:
  - Cross Cloud
release: "264"
---
# Manage Blueprints in Agentforce Operations

Maintain and evolve your blueprints over time in Agentforce Operations. Learn how versioning works, when to use collaborative editing, and what happens when you delete blueprints.

### 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="d8861e35">License Required</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d8861e35 ">
            <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>

## Why Blueprint Management Matters

Blueprints aren't static templates. They evolve as your business processes change, as you discover improvements, or as new requirements emerge. With effective blueprint management, you can make changes without disrupting running workflows, collaborate with teammates during development, and maintain a clear history of what changed and when.

The key to successful blueprint management is understanding when to create a new version and knowing which changes affect running workflows.

## Blueprint Versions

Every time you publish a blueprint, Agentforce Operations creates a new version. Versioning protects running workflows from changes that you make to the blueprint. When you edit and republish a blueprint, existing workflows continue using the old version while new workflows use the updated version automatically.

Use versions to track the evolution of your process over time. Add version notes when you publish to explain what changed and why. If you discover an issue with a new version, you can restore a previous version and republish. There's no limit on the number of versions a blueprint can have.

To learn more, see [Manage Blueprint Versions in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_manage_versions.htm&release=264.0.0&type=5 "Create new versions of blueprints, review change history, and restore a previous version in Agentforce Operations.").

## Collaborative Editing

Multiple people can edit the same draft blueprint at the same time. With collaborative editing, teams can work together on complex blueprints without interfering each other's changes. You see who else is editing the blueprint in real time, and changes appear immediately for everyone.

Use collaborative editing during initial blueprint development when multiple people must contribute different sections, or when you're making coordinated changes across stages and tasks. Collaborative editing only works on draft blueprints.

To learn more, see [Collaborative Blueprint Editing in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_collaborative_editing.htm&release=264.0.0&type=5 "Multiple people can work on the same draft blueprint at the same time. Agentforce Operations shows who else is editing and updates everyone's view in real time.").

## Deleting Blueprints

Delete blueprints that you no longer need, to keep your workspace organized. When you delete a blueprint, Agentforce Operations deletes all versions permanently. Running workflows created from the blueprint continue to run normally. Deleting a blueprint doesn't affect workflows that are in progress.

Consider whether you might need the blueprint again before deleting it. If there's a chance you might want to reuse the process structure, keep the blueprint and mark it as inactive or archive it by using tags instead of deleting it. Deletion is permanent and you can't undo it.

To learn more, see [Delete a Blueprint in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_delete.htm&release=264.0.0&type=5 "Delete a draft or published blueprint from your workspace in Agentforce Operations.").

## Locking Workflows

Lock a blueprint's workflows to prevent run-time owners from modifying stages or approval criteria after the workflow starts. Use locking when your process requires strict adherence to the defined structure. To learn more, see [Lock a Blueprint’s Workflows to Prevent Run-Time Changes in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_lock_workflow.htm&release=264.0.0&type=5 "Lock workflows from a blueprint to prevent run-time owners from modifying stages or approval criteria after you start the workflow in Agentforce Operations.").

Understand which actions are permitted and which are restricted in locked workflows, so workflow owners know what they can and can't change at run time. To learn more, see [What You Can and Can't Do in Locked Workflows in Agentforce Operations](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.").

To learn more, explore these links.

- **[Edit a Blueprint in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_edit.htm&release=264.0.0&type=5)**  
    Open an existing blueprint for editing to add stages, tasks, automations, or other changes.
- **[Manage Blueprint Versions in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_manage_versions.htm&release=264.0.0&type=5)**  
    Create new versions of blueprints, review change history, and restore a previous version in Agentforce Operations.
- **[Collaborative Blueprint Editing in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_collaborative_editing.htm&release=264.0.0&type=5)**  
    Multiple people can work on the same draft blueprint at the same time. Agentforce Operations shows who else is editing and updates everyone's view in real time.
- **[Delete a Blueprint in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_delete.htm&release=264.0.0&type=5)**  
    Delete a draft or published blueprint from your workspace in Agentforce Operations.
- **[Lock a Blueprint’s Workflows to Prevent Run-Time Changes in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_lock_workflow.htm&release=264.0.0&type=5)**  
    Lock workflows from a blueprint to prevent run-time owners from modifying stages or approval criteria after you start the workflow in Agentforce Operations.
- **[What You Can and Can't Do in Locked Workflows in Agentforce Operations](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.