The problem in two sentences
If your team still copies Opportunity or Quote data into Word and chases signatures by email, you waste hours and introduce errors. Salesforce document generation can produce multi-page PDFs from Opportunity, Contract, Quote or custom objects, file the finished document back to the record, and send it for signature without writing Apex.
Why Salesforce document generation matters for admins
Salesforce document generation gives you a clicks-first way to build and deliver documents from Salesforce data. For an admin that means fewer template maintenance headaches, predictable filing, and a consistent signing process your users can follow.
The common admin headaches this fixes
- Manual assembly: your sales reps copy Account, Opportunity and Quote fields into a long Word contract. That’s error-prone on a 60-page agreement.
- Repeatable child data: line items, fees or milestones need to repeat as table rows — not a separate document per line.
- Where to file: finished PDFs get emailed around and never attached back to the right Opportunity or Contract record.
- Signature chaos: chasing signatures for 200 renewals a month leads to a four-day signature chase on average.
How to set up Salesforce document generation (admin steps)
Below are the practical steps you can do with clicks. I’ll note the limits and choices you need to make as an admin.
1) Build your template in Word
Create a Word template with merge fields where you want Salesforce data. Use anchor tags for signature positions instead of fixed coordinates — anchor tags survive repagination for long documents. Templates can be single or multiple files; you can later bundle several templates into one signature run.
2) Map data from records
Point the template at any standard or custom object (Opportunity, Quote, Contract, Account, Contact, or my_object__c). Savvy DocuGen reaches up to five levels of parent lookups, and it supports child and grandchild records as repeating table rows — so you can include every QuoteLineItem or custom child list as rows in a table.
3) Set filing and size choices
Decide where completed documents are stored. You can file to Salesforce Files or Notes and Attachments per template. Remember Notes and Attachments is capped at 25 MB by Salesforce; templates that produce larger documents need Files. The connector accepts documents up to 40 MB.
4) Send for signature via your Circularo account
When you send the document, it uses your organisation’s Circularo account — there’s no third-party signing account to manage. Signed PDFs are written back to the same record. You can require an emailed one-time code for signer identity, and you can require a per-signer password pulled from that signer’s Salesforce record.
5) Triggering: how to start generation
Admins can make document generation start by:
- a button on the record page (quick and visible to users)
- a stage change (for example Opportunity.Stage = Closed Won)
- a field change via Flow
- a new file uploaded to the record
Use a button for ad-hoc runs and a stage or field-based trigger for repeatable automation.
Permissions, storage and sandbox considerations
Permissions
Because Savvy DocuGen connects through an authorised connection rather than a managed package, there’s nothing to install. Your security team won’t be reviewing a package, but you still need to manage access: users who send for signature should have the right object-level and field-level access, plus access to the destination Files folder if you restrict File visibility.
Storage and file size
Decide up front whether finished PDFs go into Files or Notes and Attachments. Use Files when documents may exceed 25 MB, since Notes and Attachments is capped at 25 MB and cannot be changed. The connector supports documents up to 40 MB.
Sandbox parity
The connector works in sandboxes exactly as in production. That means you can build templates, test anchor-tag signatures, and verify filing without affecting live data.
Quick admin checklist before you roll out
- Create and test Word templates with long content and repeating tables (include a 60-page sample to validate repagination).
- Use anchor tags for signature fields so signature positions survive page breaks.
- Decide whether signed PDFs should go to Files or Notes & Attachments; choose Files for any file >25 MB.
- Map signer identity: enable one-time code or per-signer password fields on the Contact or User record.
- Test triggers in a sandbox: button, flow-based field change, and stage change scenarios.
- Train reps on a single button or process so signed documents end up attached to the correct Opportunity, Contract or Quote record.
If your org generates regular agreements or bundles multiple templates into one signature run, these steps stop the copy-paste and chasing cycle fast.
Savvy DocuGen fills Word and PDF templates from any Salesforce record, handles parent and child data, files finished documents back to the record, and sends for signature through your Circularo account using anchor tags and optional signer verification. Try it in your sandbox — set up one template, map a repeating table, and send a test signature to see how it files back to Opportunity or Contract.
Read next