---
schema_version: "1"
id: d192855ab4fbefe9d74de7b63bf2074727bed584fa416e8f822957ecb7610378
title: Designate a Workflow Owner 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_workflows_owner.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_workflows_owner.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: aa6682e34214b57a9f94f3ec401d52bc05b6e89f298f5ea6212b24f51fa7b800
description: Assign ownership of workflows to a user or team that's different from the user who created the blueprint in Agentforce Operations.
products:
  - Cross Cloud
release: "264"
---
# Designate a Workflow Owner in Agentforce Operations

Assign ownership of workflows to a user or team that's different from the user who created the blueprint 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="d14560e39">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e39 ">
              <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="d14560e73">Role or Access Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e73 ">To create a blueprint from scratch, using AI, or by importing a .rex file in
              Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e73 ">Admin role or Creator role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e73 ">
              <p style="margin-bottom:0;">To create a blueprint by importing a .docx file in Agentforce Operations:</p>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e73 ">Admin role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e73 ">To publish a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e73 ">Admin role or Publisher role with View access for the blueprint</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e73 ">To edit a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d14560e73 ">Admin role, Creator role, or a user with Edit access for the blueprint</td>

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

The user who creates a blueprint isn't always the right user to own the workflows that run from it. For example, a team admin can build and publish a blueprint, but a separate team or user is responsible for managing the workflows it generates. With Agentforce Operations, you can designate a workflow owner in the blueprint so that every workflow started from it is automatically assigned to the right user or team.

You can designate only one user or team as the workflow owner at a time. The workflow owner or a workspace admin can transfer ownership after a workflow is created. Learn more in [Transfer Ownership of an Active Workflow in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_transfer_workflow_ownership.htm&release=264.0.0&type=5 "Reassign ownership of a running workflow to a new user or team when the current workflow owner leaves the organization or changes roles in Agentforce Operations.").

1. [Create a blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") or [edit an existing blueprint](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.").
2. In the blueprint, click the **Access** tab.
3. In the Workflow access section, click the **\+ Set workflow owner** field.
4. Search for and select the user or team that you want to assign as the owner of workflows started from this blueprint.
5. Publish the blueprint.
    
    To learn more, see [Publish a Blueprint in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_publish.htm&release=264.0.0&type=5 "Publish a blueprint to make it available for others to use in Agentforce Operations.").

The workflow owner receives an email notification when the blueprint is published. All workflows started from this blueprint are automatically assigned to the designated owner with edit access.