How to Set Up a Document Generation Approval Workflow in Salesforce

Most document generation workflows need a review step before anything goes to a customer. A legal team needs to check a contract. A manager needs to approve a proposal. A finance lead needs to sign off on an invoice above a threshold. Automating document creation without automating that review step just means mistakes get out the door faster, which isn’t really the goal. This post covers how to build that approval layer into your Salesforce document generation workflow using Approval Processes and Flow, so review happens automatically without slowing the whole process back down to manual speed.

Review built in, not bolted on. See how approval fits the workflow.

Book a demo 

What a Document Generation Approval Workflow Looks Like 

That is the ideal end state to aspire to: the representative creates the document from the Salesforce record, it is routed to the proper person for approval, who approves or rejects the document, and then the document is sent to the client or forwarded out for electronic signature – all without ever leaving Salesforce or having to chase an approval through email or Slack. 

That last part matters more than it sounds. A lot of “approval processes” in practice are really just a Slack message asking “can you check this before I send it,” which technically works but leaves no clean audit trail and depends entirely on someone remembering to ask. A proper document generation approval workflow makes that review step structural rather than optional, built into Salesforce itself so it happens the same way every time, regardless of who’s generating the document or how busy the approver is that day. 

Option 1: Approval Before Document Generation (Approve the Deal First) 

One approach gates generation itself. The Opportunity or record must be in an Approved status before the Generate Document button even becomes available, which means the review happens before a document exists at all rather than after. 

This works through field-based visibility rules or Quick Action conditions restricting generation until a specific field, often a picklist value like Approval Status, equals Approved. Practically, that means a rep opens the record, sees the Generate Document action isn’t available yet, and knows immediately that the deal itself still needs sign-off before any paperwork gets built. It’s a clean approach for situations where the terms of the deal are what actually need review, pricing, discount level, contract terms, rather than the document’s wording specifically. Once the underlying record is approved, the document that gets generated from it reflects already-approved terms, so there’s less need to re-review the document itself afterward. 

Option 2: Approval After Generation, Before Delivery 

The other approach flips the order. The document generates and saves to the record first, but delivery is held back until an approver has actually reviewed the finished file, not just the underlying deal terms. 

It can be used where the content of the document is important, the legal language, the format or the attachments, which a manager or a lawyer wants to view in their final form before delivering it to the customer. There are two common approaches to create such a feature. The first one includes the use of the Salesforce Approval Process for custom Document Review object, which allows to send the document for review as a separate record.  

The other uses a Flow wait element, generating the document, then pausing the Flow until an approval field on the record gets updated, at which point the Flow resumes and triggers delivery. Both approaches land in the same place: nothing goes out until someone with the right permission has actually looked at the finished document. 

Let’s build real approval into your workflow. 

Schedule a call

Step-by-Step: Building an Approval Process for Document Review 

This section walks through building the review-after-generation approach using a native Salesforce Approval Process, which tends to be the more straightforward path for teams that don’t need Flow’s added flexibility. 

Step 1: Create the Approval Process on the relevant object, either the Opportunity itself or a custom Document object if you’re tracking generated documents as their own records. 

Step 2: Set entry criteria so the process triggers automatically when Document Status equals Pending Review, meaning the Approval Process only kicks in once a document has actually been generated and is sitting ready for someone to look at. 

Step 3: Configure the initial submission action to notify the approver by email the moment the record enters the approval process, so there’s no delay waiting for someone to happen to check their queue. 

Step 4: Set the approver, which can be a specific user, the submitter’s manager, or a role hierarchy lookup if approval routing needs to change depending on who submitted the document or which team it belongs to. 

Step 5: Configure the approval action to update Document Status to Approved when the reviewer signs off, which is the field change that everything downstream, covered in the next section, will be watching for. 

Step 6: Configure the rejection action to update Document Status to Rejected and notify the original submitter, so a rejected document doesn’t just sit silently, someone knows immediately that it needs revision. 

Step 7: Activate the Approval Process. Test it with a real submission before rolling it out broadly, confirming that notifications fire correctly and both the approval and rejection paths update the Document Status field as expected. 

Triggering Document Delivery After Approval Using Flow 

Once the Approval Process updates Document Status to Approved, that field change needs to actually trigger something, otherwise the document sits approved but undelivered, which defeats the purpose. 

A Record-Triggered Flow set up to fire on that specific field change handles this cleanly. Configure the Flow to trigger when Document Status changes to Approved, and add an action that delivers the document, either emailing it directly using the delivery methods covered in a related guide on Salesforce document generation, or routing it out through Salesforce esignature integration for signature collection if the document requires a signed copy back. This is the connective tissue between the approval step and the outcome the whole workflow exists for: an approved document that actually reaches the person who needs to sign or receive it, without anyone manually triggering that final step. 

Approval for Bulk Document Generation 

Approval logic gets more interesting once you’re generating documents for multiple records at once rather than one at a time, since reviewing hundreds of individual documents isn’t realistic for most approval processes. 

One approach uses sample approver review before the full batch runs, an approver checks a handful of representative documents generated from a small sample of records, confirms the template and data are populating correctly, and approves the batch to proceed at full volume. This works well when the risk is mostly about template accuracy rather than deal-specific terms, month-end invoices generated from a consistent template, for instance. 

The other approach applies post-generation review before delivery at the batch level, the entire batch generates first, and an approver reviews a summary or spot-checks a portion of the output before the delivery step, whether email or eSignature routing, actually fires for the whole batch. This fits situations where the approver wants visibility into what was actually produced, not just confidence that the template was configured correctly ahead of time.