Branches for Vault — How To Use

End-user guide. Target: Autodesk Vault Professional 2026.

What it does

Vault has versions, revisions and lifecycles — but no branches. Branches for Vault adds Git-style branching: create an independent, tracked copy of a design, work on it in parallel without touching production, compare it against mainline, and merge it back as a new version — with full history preserved on both sides.

1. Installation

Run deploylocal-client.bat (dev) or the client installer (release). It places the add-in in C:\ProgramData\Autodesk\Vault 2026\Extensions\BranchesForVault. Start Vault Client 2026 and log in. Uninstall = delete that folder.

2. Create a branch

  1. In Vault, right-click a file or a folder (e.g. an assembly Assembly1.iam).
  2. Branches for Vault → Create Branch…
  3. Enter a branch name (lowercase, digits, dashes — e.g. tender-acme).
  4. Click Resolve scope to preview which files will be copied, then Create branch. A full, lineage-tracked copy appears under $/Branches/{project}/{branch}.

3. Work in the branch

Check out, edit and check in the files under $/Branches/... exactly as you would any Vault file. Production (mainline) is untouched. Each check-in is a "commit" on your branch.

4. Review changes and merge

  1. Open Tools → Branches for Vault — Branch Manager.
  2. Select your branch → Compare with mainline. Each file shows: Changed in your branch (ready to merge), Also changed in mainline (conflict, needs a choice), or Unchanged.
  3. For any conflict row, pick TakeBranch or KeepMainline in the last column.
  4. Click Merge to mainline. You'll see a dry-run preview of exactly what will be written; confirm to execute. Each merged file becomes the next version on mainline — nothing is overwritten.

5. Abandon a branch

If a branch isn't going forward, select it → Abandon branch. The copied files stay in Vault; the branch is closed and removed from the active list.

Honest limitations

  • Binary CAD files can't be content-merged; a merge chooses which version wins per file.
  • Reference re-linking on Get needs a correctly installed Inventor/Apprentice engine on the machine (as with native Copy Design).
  • v1 covers files/assemblies. Items and BOM master are planned for v2.

Support

support@avantleap.com

Branches for Vault — How To Use | Avant Leap