Locking Assets in Version Control

Plamen
Plamen
  • Updated
Feature availability 🛈
⭕ Personal ✔️ Suite

The Lock Assets feature in Version Control helps prevent conflicting changes in collaborative workflows. It provides a simple way for users to visually indicate they’re working on an asset while ensuring a version is safely stored in the cloud.

Assets can be locked from the context menu, and only the user who applied the lock can remove it. Locked assets are marked with an icon, and other team members can’t perform the following actions:

  • Add to Version Control.
  • Add Variant.
  • Rollback to Version.
  • Remove from Version Control.

NOTE: For complex files (e.g., scenes with multiple linked files), it’s recommended to lock all related files.

Lock assets.

The lock icon uses color to indicate ownership:

  • Green: Assets locked by you.
  • Orange: Assets locked by another team member.

Asset locked by another user.

NOTE: You can technically apply a lock to local items, but it won’t have any effect. Locking only works for assets managed in the Version Control or Hybrid DAM (HDAM) systems to prevent accidental overwrites.