The problem: edits to document templates overwrite live agreements
If you change a clause in a Word template and that template is used again, you’ve just altered the wording for new documents and possibly for historical expectations. Salesforce template versioning and document templates Salesforce management are usually an afterthought, so an admin fixes a single error and suddenly salespeople complain that signed Contracts look different to what legal approved.
This happens most often with long documents: a 60-page master services agreement with five annexes, or a Quote PDF assembled from multiple templates. Imagine 200 renewals a month where you need one approved clause to differ depending on the billing cycle — that becomes a mess fast.
Salesforce template versioning: naming and permissions
Start with rules you can enforce without code. Naming alone prevents half the mistakes.
Enforce a strict filename convention
- Use a template name like:
MSA_v2024-06-01_legal-APPROVED.docx — include version, date and owner.
- Keep draft copies in a folder that only the template editors can access:
/Templates/Drafts/. Move approved templates to /Templates/Approved/.
- Do not reuse filenames. If you need an edit, save as a new version — never edit the approved file in place.
Permissions and a single point of truth
Limit who can edit approved templates. Use Permission Sets or a narrow profile: only Legal or a designated Template Owner should have Edit access to the Approved template folder. Clicks not code: create a Public Group called "Template Editors" and give them access to the draft folder; remove Edit access from everyone else.
Document templates Salesforce: store and track the version used
It’s not enough to control filename and folder. You must record which template version produced each final document.
Record the template version on the record
Add a text field on the object that receives the merged file. For example, on Contract or Opportunity add Doc_Template_Version__c. When a user clicks "Generate Document" they should set that field to the template name and version used.
How to make that click-friendly
Use a Lightning Flow or a quick action button. The Flow can present a picklist of approved templates (read-only list from a custom metadata type or a small custom object like Doc_Template__c) and then:
1. Ask user which template (picklist) and which bundle if needed.
2. Call the DocGen button to fill the selected template.
3. Set Contract.Doc_Template_Version__c = selected template name.
4. Save the generated file to the Contract record.
This keeps the action within a couple of clicks and ensures the org knows which template created each file.
A repeatable, click-based process for admins
Admins don’t want to write Apex for this. Here’s a process you can implement with Clicks and standard metadata.
Step-by-step checklist
- Create a small custom object
Doc_Template__c with fields: Name, Version, Active (checkbox), Doc_Type (MSA, Quote, NDA), and File_Link (File or URL).
- Upload template files into a protected Salesforce Files folder. Link them from
Doc_Template__c.
- Build a Lightning Record Page component or a Flow screen that shows only Active templates for the Doc_Type of this record.
- Add a quick action to Opportunity, Quote or Contract that launches the Flow and then triggers document generation.
- Use a validation rule: if Contract.Status = 'Signed', prevent changing
Doc_Template_Version__c or the attached signed file. That protects historic records.
Archiving and audit
When a template is superseded, mark the prior Doc_Template__c as Inactive and move the file to an archive folder. Don’t delete. If you ever need to reproduce a legacy document exactly as it was, you must be able to re-run the merge with the original template file.
Concrete scenario: a clause change during a renewal wave
Say legal updates an indemnity paragraph mid-month. You’ve got 200 renewals in the pipeline and sales reps are pushing to generate documents. If editors overwrite the approved MSA file, the next batch of merged documents will carry the new wording — and you’ll have no record of which renewals used which text.
Following the steps above you: (a) create MSA_v2024-06-01 and a new MSA_v2024-06-15, (b) mark the new one Active, (c) leave the old version Inactive but available for re-merges, and (d) ensure every Contract.Doc_Template_Version__c stores the exact version used. That prevents rework, and legal can audit which customers signed which wording without digging through Files one-by-one.
How Savvy DocuGen fits this pattern
Savvy DocuGen fills Word and PDF templates from any Salesforce record and can write the finished document back to the record as a File. Use it with the click-based Flow above: select template version from your Doc_Template__c list, let DocuGen merge the chosen template (including child record tables and up to five levels of parent lookups), and have the signed PDF returned to the same record. It supports bundling several templates into one signature run and keeps signature positions stable with anchor tags, so you don’t need to rework positions when pagination changes.
If you want to try this in your sandbox, install no package — connect Savvy DocuGen through an authorised connection and run your Flow the same way as in production. Try it in a sandbox today to confirm template naming, Flow prompts, and the template version field behave the way you expect.
Ready to try this in your sandbox? Connect Savvy DocuGen and run a few merges from a test Opportunity to see template versioning end-to-end.
Read next