The short answer: After installing the Notarize with Proof Salesforce App, most organizations add a document generation tool to automate document prep — pulling Salesforce data into ready-to-sign templates. You can optionally use Proof's White Text Tags to pre-place signer, notary, and document fields inside those templates, eliminating manual field placement during the signing session. White Text Tags must be enabled by Proof and require .docx format — they do not work with PDFs.
How Document Generation Fits Into the Workflow
Without a document generation tool, someone on your team manually creates and uploads documents each time a transaction is initiated. A document generation tool replaces that step — it pulls data from Salesforce records (contacts, opportunities, accounts) and produces a completed document automatically.
That generated document is then uploaded into a Proof transaction — either manually or via the Salesforce integration — where signers review and sign it. Common document types include powers of attorney, leasing agreements, loan disclosures, and contracts.
Adding White Text Tags to your templates takes this further: signer, notary, witness, and document fields are pre-placed in the template, so they appear automatically in the right locations when the document is uploaded to Proof — no manual tagging required.
White Text Tags
White Text Tags are hidden field markers embedded directly in a Word document template. When the document is uploaded to Proof, the platform reads the tags and automatically places the correct fields — signer signature, notary seal, date, and others — in the right locations.
White Text Tags require .docx format. They are not supported in PDF documents. If your document generation tool outputs PDFs, White Text Tags will not function.
White Text Tags must also be enabled for your Proof organization before use. Contact your Customer Success Manager or support@proof.com to request enablement.
Common Use Cases
- Automatically generating contracts from Salesforce opportunities
- Creating pre-filled notarization documents from CRM data
- Reducing manual data entry during transaction preparation
- Generating signer-ready leasing and lending documents
- Embedding signer and notary fields directly into generated documents via White Text Tags
Commonly Used Salesforce Document Generation Apps
Conga Composer
Generates branded, data-driven documents automatically from Salesforce data sources.
Website · AppExchange Listing
Nintex Drawloop DocGen
Automates document generation workflows directly from Salesforce records and processes.
Website · Pricing · AppExchange Listing
Formstack Documents
Automates document generation and proposal workflows using Salesforce data.
Website · Pricing · AppExchange Listing
Drive Connect
Links Google Drive files to Salesforce records and supports Google Docs generation from Salesforce data.
Website · Pricing · AppExchange Listing
Best Practices
- Standardize your Salesforce document templates before deploying automated workflows into production.
- Test all document templates in a sandbox environment before rollout.
- Validate White Text Tag placement before sending signer transactions — confirm your document generation tool outputs .docx, not PDF.
- Use standardized Salesforce data fields to reduce template inconsistencies.
- Review generated documents for formatting and signer field accuracy before going live.
- Restrict template editing permissions to authorized administrators.
Troubleshooting
- Signer fields are missing after upload — Verify White Text Tags were configured correctly and that the document was uploaded as a .docx file, not a PDF.
- Generated documents contain incorrect Salesforce data — Validate the mapped Salesforce fields and source records in your document generation tool.
- Generated documents fail to upload into Proof — Verify the generated file format is supported. If using White Text Tags, the file must be .docx.
- Document formatting appears incorrect — Review the document generation tool's template settings and merge-field formatting.
- White Text Tags are not being recognized — Confirm White Text Tags are enabled for your Proof organization. Contact your Customer Success Manager or support@proof.com if not.
Summary Checklist
- The Notarize with Proof Salesforce App is installed and configured before setting up document generation.
- I've selected and configured a Salesforce document generation tool compatible with my workflow.
- If using White Text Tags: they are enabled for my Proof org, my templates are in .docx format, and tags have been validated in a sandbox.
- All document templates have been tested in a non-production environment before rollout.
Still Unsure?
Our support team is happy to help. Submit a support request or chat with us from any page in the app.
Updated