2993 results found
-
Allow users to configure the "next" button on the template level for signers via API
We often have issues where clients send a document to someone to sign and a number of non-required fields are missed. When the signers use the "next" button, it jumps from one required field to the next, meaning intermediate non-required, but important fields are missed.
1 vote -
Collect Form Data
Ability to use an existing form on the Collect Form Data in Workflows.
1 vote -
Bank Transfer as a Payment Method via Stripe in PandaDoc
We would like to offer bank transfer as a payment method using Stripe as the payment gateway. A workaround where customers transfer funds directly to our account isn't very practical because we can't automate the process that way. Please make bank transfer available (alongside SEPA and credit card).
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 -
Native Support for Salesforce Product Groups in PandaDoc Documents
Summary:
When using PandaDoc's Salesforce integration, customers are unable to carry over native Salesforce product Groups into their PandaDoc documents. Groups exist at the Salesforce UI level but there is currently no mechanism to pass them through to PandaDoc automatically.Desired Behavior:
When a document is generated from a Salesforce Opportunity, PandaDoc should automatically recognize and reflect the product Group structure. organizing line items into their respective groups as sections within the document.1 vote -
Select Multiple Templates for Bulk Send
the ability to select multiple templates at once in bulk send
2 votes -
Apply automation to a Workspace
Need the ability to set up an automation for a workspace. For instance, any completed document is directed to a workspace cloud location like BOX for archiving. Currently have to remember to set up automation for each template or document which can lead to missed archiving.
1 vote -
SMS verification should be Part 11 workspace default setting
For 21 CFR Part 11 workspace the Identity Verification should default to SMS setting for any signer added to a document or template AND the contact's phone number should auto populate.
1 vote -
Auto populate SMS phone numbers from domain / workspace user contact information
Extremely annoying for originator to have to enter signer phone number each time for SMS verification. Team members in the domain / workspace should have phone numbers auto populate in SMS field in when setting up templates and documents.
1 vote -
Dynamic "Required Fields" Progress Counter
The recipient view displays the total number of required fields in the document, regardless of whether they have already been populated. For example, if a document contains 20 required fields and 18 are pre-filled via the API, the counter still displays "20 fields required."
Proposed Improvement: Update the counter to reflect only the incomplete required fields. In the scenario above, the UI should dynamically update to show "2 fields remaining."
For customers who pre-populate the majority of their document data via API, the current counter is misleading and potentially impacts completion rates as recipients think they need to complete more…
3 votes -
Auto Detect and Placement of Variables
When uploading a Word document that already contains variables written in brackets (e.g., [Client.Name], [Company]), PandaDoc does not recognize them. They come in as plain text and each variable has to be manually recreated inside the editor one by one.
Auto-placement already works for fillable fields on DOCX import, so the expectation is that variables would behave the same way. For templates with a large number of variables, having to rebuild them manually after every upload adds significant time and friction to the workflow.
Requested behavior:
PandaDoc should automatically detect bracket-style placeholders on DOCX import and register them as variables…1 vote -
Filter organization-wide document list by recipient email
Currently, the Document Efficiency report under Reports provides an organization-wide view of documents, but recipient email is not available as a filter. The only workaround is to export the full data CSV and manually filter the "document recipient" column outside of PandaDoc.
What we're asking for: Add recipient email as a filterable field in the Document Efficiency report (or equivalent org-wide document view), so admins can quickly pull all documents sent to or received by a specific recipient without needing to export and process data externally.
Use case: Admins need to audit all documents associated with a specific contact —…
1 vote -
Selecting Time zone for Sydney Australia (UTC +11) AEDT
Selecting Time zone for Sydney Australia (UTC +11) AEDT in the Document settings
4 votes -
Option to Enable Dark mode
Would like to have the option to enable this when navigating document lists, statuses, etc. (outside of Editor)
1 vote -
Fix field-tags docs: examples show square brackets, but only curly braces parse
The docs page https://developers.pandadoc.com/docs/field-tags shows square-bracket
examples like [textfield:user:name], but the API only recognizes curly-brace
tags ({textfield:user:name}). Support chat confirmed curly is the correct
syntax. Two asks:- Update every example on that page to curly braces.
- Make unparseable/bracket-style tags return a validation warning instead of a silent no-op — today the doc uploads fine with zero fields and recipients silently degrade from signer to CC, which you don't notice until someone can't sign.
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 -
MondayCRM automations
- Change MondayCRM task's column status when document is sent
- Change MondayCRM task's column status when document is completed
- Attach PDF to MondayCRM task when document is completed
1 vote
- Don't see your idea?