Workflow deployment elements trigger project asset locking as follows:
If the project workflow includes staging and production targets, project assets are locked when a user approves deployment to staging.
If the project workflow includes only a production target, assets are locked when a user approves deployment to production.
In both cases, assets remain locked until deployment to production is complete and verified. At that point, the workflow checks in project assets and unlocks the assets. Until then, other projects cannot deploy those assets. You can determine which assets are locked by other projects by opening the project’s Lock Conflicts tab.
If projects routinely contain large numbers of assets, you can optimize asset locking in order to advance the project workflow more quickly. See Optimizing Workflow Performance in the Setting Up an Asset Management Server chapter.
Note: Project assets can be deployed to one-off targets at any stage of the project’s workflow, whether locked or unlocked. For more on one-off targets, see One-Off Deployments in the Deployment Concepts chapter.
