3799 results found
-
Assign fields automatically when document us upload
For field conversion, allow a default option to assign all fields to one specific role after the document is created. Customer had an issue with the process documented here and it did not work:
https://support.pandadoc.com/en/articles/9714596-field-auto-placement2 votes -
Lock recipient selection in Multiple-item/Multiple-section selection mode
Customers using “Multiple-item selection” or “Multiple-section selection” want items pre-selected but not editable by the recipient. Currently impossible — these modes always show interactive checkboxes, and row-level “Optional items”/”Edit quantity” toggles only apply in Customized selection mode. Workaround (Customized selection + no optional rows) removes the pre-selected multi-item display. Requesting a way to lock recipient interaction while keeping this display mode.
2 votes -
Failure Notification email setup
To include Failure Notification email setup
1 vote -
Support user details (name, email) as token values for custom HubSpot User-type deal properties in HubSpot
When a HubSpot deal property of type “HubSpot User” is used as a PandaDoc token/variable, it currently only returns a raw numeric ID instead of the actual user’s information. The native Deal Owner field already works correctly, it resolves to readable user details. So the expectation is that custom HubSpot User-type properties should behave the same way.
2 votes -
QES feature to comply with Swiss standards
PandaDoc QES (Qualified Electronic Signature) feature to comply with Swiss standards, where regulations are stricter.
1 vote -
Address autocomplete or verification for City and ZIP fields
When recipients type their address into PandaDoc fields, typos in City and ZIP code are common. Current field validation only checks the format, so misspelled cities and incorrect but valid-looking ZIP codes still pass. This leads to inaccurate data, especially for customers who send completed field data to other systems through integrations or the API. Adding every possible city to a dropdown manually isn’t practical.
The request is for an address autocomplete or verification field that fills in City, State, and ZIP automatically. An alternative would be dependent dropdowns, where choosing a State loads its valid Cities and ZIP codes.
1 vote -
2 votes
-
Recipient-Editable Unit Price in Pricing Table with Salesforce Sync
Allow recipients to edit the Unit Price / Sales Price of Opportunity Products directly within the PandaDoc Pricing Table during the signing process, with the ability to sync the updated value back to the corresponding Salesforce Opportunity Product record.
2 votes -
Add Collect files/File Upload field to Smart Forms
Description:
Smart Forms don’t currently support file uploads from the recipient. The Collect files field is available in templates and documents, but it isn’t in the Smart Form field picker. Recipients can only attach files inside the generated document after they submit the form.
Current behavior:
The Smart Form field picker offers Short text, Long text, Number, Email, Phone number, Date, Multiple choice, Checkboxes, Dropdown, and Layout blocks (Title, Image). There is no file upload option.
Workaround: add a File Upload Field to the template behind the Smart Form, so recipients attach files in the document after completing the form.…
1 vote -
SSO: Independent Idendtity for Affected Branches Account
SSO: The main account has SSO setup, there should be a way or function to separate the main account and the branches account that shares the same domain configured in SSO
1 vote -
HubSpot deal tax rate in pricing tables in MCP
The tax rate from HubSpot in the pricing table: our VAT rate depends on the client's region and is already on the deal, so filling the table's tax from a deal property, the way merge fields fill deal data, would give every document the right rate from the start.
2 votes -
Linked HubSpot objects in the PandaDoc MCP server
Linked HubSpot objects in the PandaDoc MCP server
2 votes -
Global Email Templates
Ability to share email templates across multiple workspaces similar to how you can share templates.
1 vote -
Allow requester to attach files in message to approver
After clicking the "Send for approval" button, the requester is given the option to write a message to the approver. Please allow users to also attach files to the message, which might help give context for the approval request.
1 vote -
When posting, it helps to include: A clear title (e.g., “Allow adjustable transparency for email background color”) Your use case Current li
Allow adjustable transparency for email background color
Current limitation (no fade control)
Expected behavior (user-controlled opacity)
Branding is a must-colors are direct source of placement and this is too easy to make happen. You can create smooth color fade changes using CSS Transitions for interactive elements or CSS Gradients for static transitions.1 vote -
Ability to set the position of the bundled document when adding it via API call
At this point, when adding bundled document via /sections/uploads, it always appears at the end of the initial document.
It would be great to have the parameters such as order or position to control the location of the newly added document (i.e. if I set up "bundle_position": "0", the system will add my document to the very beginning).
2 votes -
Set a document status for documents that have recently been renewed/grown out of its term.
I am trying to set a document status for documents that have recently been renewed. I would like to set completed documents to something like "expired" and let only one remain on completed. This way we can easily see which one is the most recent document in the folder.
1 vote -
Export Document Data: API
Not really. i know i can export the data to csv however, i am automating the extraction process by using the API key to call the data into another system where i can use it for reporting. The production API pulls tokens, variables and some fields from documents but it does not pull data manually entered into the "Review Data" form. this is the challenge. How can the API pull that manually entered data? see the screenshot i sent to you earlier.
2 votes -
API endpoint to delete a single Collect Files upload without deleting the whole document
There's currently no API endpoint to remove just a Collect Files field's uploaded file from a Completed document — the only option is deleting the entire document via the API, which also removes its PDF, certificate, and audit trail. Customers using Collect Files for identity verification need a way to purge just that file after a retention period (e.g., 180 days) while keeping the document itself intact.
2 votes -
Separates "add/manage recipients" from "edit document content."
The ability to have certain users only creating the documents but not be able to add signers .
1 vote
