You are here:
Lock workflows from a blueprint to prevent run-time owners from modifying stages or approval criteria after you start the workflow in Agentforce Operations.
| License Required |
|---|
This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Operations license. To purchase an Agentforce Operations license, contact your Salesforce account executive. |
| User Permissions Needed | |
|---|---|
| To lock a blueprint's workflows in Agentforce Operations: | Admin role, Creator role, or Edit access on the blueprint |
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.
To learn more, see What You Can and Can't Do in Locked Workflows
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.