2929 results found
-
Localize system variable values based on Recipient View Language
Description: System variables (e.g. company address, sender details) always display in English regardless of the Recipient View Language setting. These values should respect the configured language so that all content — including variable-populated fields — is presented consistently in the recipient's language.
1 vote -
Slide show of multiple images in a document
Ability to add a slide show of multiple images in a document
1 vote -
Review and Sign Later
A feature where a recipient can receive a notification to review the document only, without requiring a signature, and after another recipient completes the signatures, a notification can be received again for signature.
This will allow the recipient to review first or be notified when a document has been triggered without any signature or action.
2 votes -
QES available via API
QES available via API - Needs QES enabled automatically in a Make (Integromat) workflow when creating a document from a template.
2 votes -
Save Headers and Footers to Content Library (and reuse across documents)
Description: Allow headers and footers to be saved as Content Library items so they can be reused and transferred into different documents. Today, headers and footers can only be added on Blank pages, and when you save a whole page as a Content Library item, the header and footer design does not save. This makes it hard to keep branding consistent across documents created from drafts or other starting points.
Use case: Create a document from a ChatGPT draft (through the integration), then quickly drop in the saved header and footer to make it “send ready” without rebuilding the header…
1 vote -
Hidden Variables in Documents - CSV-Populated Field Not Visible to Recipients
Users need the ability to include a variable in a document template that can be populated via CSV during Bulk Send but remains invisible to recipients. The primary use case is embedding internal tracking identifiers (e.g., workflow tags, custom IDs) for retrieval via the API — without exposing that data in the recipient-facing document. Current workaround is setting the variable's font color to white, which is fragile and unsupported. A native hidden/metadata field option would eliminate this friction.
1 vote -
Unsupported tiered prices from Hubspot
I would like that the integration Pandadoc - Hubspot could support the tiered prices of products from Hubspot. This means that with one product in Hubspot the unit prices changes based on the quantity you add as line item . Now Pandadoc doesn't recognize the prices of the products and its price in the Quote Builder is 0, when in reality it is not.
2 votes -
Ability to reorder documents in Rooms
Enable users to arrange the sequence of documents in the Room based on preferred importance and priority.
3 votes -
Customizing the UI text/prompts during signature or payment
We're using the Enterprise version, so totally fine if this feature remains Enterprise-only. After working on the white-labeling process, we found that this would improve the experience for our prospects and clients and enhance our brand voice.
Replacing PandaDoc's icons/symbols (such as the signature or credit card icon) with our company logo within the signing or payment modals
Customizing the UI text/prompts in those modals (e.g., changing "Complete this document and pay" or "Make a payment" to a custom copy)
According to PandaDoc CS, these interface elements are part of PandaDoc's standard recipient experience and are not customizable at this…
1 vote -
Multiple Smart Content conditions
Smart Content blocks only show the FIRST matching condition's content. If a client buys multiple products, only one product's information appears.
Request: Allow MULTIPLE conditions to apply simultaneously, so all purchased products' information shows. Makes automation actually work for multi-product scenarios. This helps other Enterprise customers with bundled services.
2 votes -
Pass PandaDoc document status to Salesforce custom fields
A way to write the PandaDoc document status back to a custom Salesforce field.
I understand that we currently have the "Change Opportunity Status" trigger available; however, the customer would like the PandaDoc document status to be automatically synced to their custom Salesforce field/object called "PandaDoc Document Status."2 votes -
Ability to create a single contract that links to multiple opportunities or deals in a CRM with automations for them all.
Some clients manage complex accounts where multiple reps are working multiple deals simultaneously — each tracked as a separate opportunity. However, when it comes time to execute, all of those deals are consolidated into a single contract.
The current automation only applies to the primary opportunity, which means once the contract is signed, there's manual backend work required to update the remaining opportunities.
The ability to link multiple opportunities to a single contract would eliminate that manual overhead and ensure automation fires accurately across all associated deals.1 vote -
Select Multiple Templates for Bulk Send
the ability to select multiple templates at once in bulk send
2 votes -
Allow "Mark as Paid" for documents in Sent/Pending status (no recipient action required)
Description:
Currently, the "Mark as Paid" option in the Payments dashboard is only available when a document is in Waiting for payment status. This requires the recipient to have opened or completed the document first. However, in cases where payment is collected outside of PandaDoc (bank transfer, check, etc.) and the document has no outstanding recipient actions, users have no way to update the payment status without involving the recipient. Request: allow users to manually mark a payment as paid regardless of document status, or at minimum when the document is in Sent/Pending status.1 vote -
Trigger Payment Flow When Manually Completing a Signed Document
When a document is manually moved to "Completed" (to reflect an offline/outside signature), any attached payment step is silently bypassed. There should be a way to still trigger or prompt for payment collection in this scenario.
Current Behavior - If a signer executes a contract outside of PandaDoc and you manually update the document status to Completed, the payment block attached to that document is skipped entirely. The only workaround is to collect payment through a separate tool and then manually mark the document as Paid in PandaDoc.
Expected Behavior - When manually completing a document that has a payment…
1 vote -
Log the document reminders auto sent to HubSpot
I'd like the document reminders that I specify on my PandaDocs that are automatically sent to get logged back to the relevant records in HubSpot (deal, contact, company). I'm hoping that will show in the Emails and All Activity sections to give me a clearer picture of activity on my Deals.
1 vote -
Remove opt-out/reporting links from white-labeled delivery emails
As a professional services firm using PandaDoc for client proposals and engagement workflows, I would like the ability to disable or customize opt-out/reporting links in white-labeled delivery emails.
These links can create confusion for clients, weaken the premium branded experience, and unintentionally reduce trust during sensitive onboarding workflows such as accounting, tax, legal, or advisory engagements.
Ideally, firms using custom branding and verified sending domains should have an option to:
remove “report spam” style messaging,
customize footer language,
or use a cleaner fully white-labeled email experience.This would significantly improve the client experience for firms using PandaDoc as a client-facing…
1 vote -
Fill in then Sign Later
A signer can complete and fill in the documents first, and once the reviewer or approver has reviewed them, the agreement or document will be returned to the client for the official signing.
2 votes -
Recipient group in/with Salesforce
Would like the ability to use recipient groups when creating a document via Salesforce
2 votes -
Push PandaDoc Form responses to Salesforce records natively
Currently, PandaDoc Forms can collect data and trigger document creation, but there is no native way to push form submission responses directly into Salesforce to create or update records (including custom objects).
2 votes
.png){kind=link}
- Don't see your idea?