5367 results found
-
Add CC Recipient to 21 CFR Part 11-compliant document
Ability to add CC recipients on CFR compliant documents.
1 vote -
Do not sign before or set a window/timeframe to sign
I would like the ability to set a timeframe in which a client can sign their document, such as no sooner than 30 days before the expiration date. Our process specifically requires their signature to be within 30 days of the planned service date for legality. We would like clients to be able to see and review the document before then, but not allow them to sign it until a specific timeframe. Rather than fill in a data manually, we would like to select something like expiration date minus 30 days as the soonest signing date so that it auto-calculates…
1 vote -
Status: different status after each signer has signed and it has been sent to the next recipient
Currently, when a document has been signed and sent to the next recipient, the document stays in viewed status; however, we would like the status to change to something else so that we can see the document has been signed by one recipient, but not the other
2 votes -
Bulk update document expiration date
Have the ability to update documents expiration dates in bulk. For example, all of the documents in one bulk send or all documents set to expire on the same date can be updated to a different date all at once.
1 vote -
Create Bundled Products via API
the ability to create bundled products via API
3 votes -
ne-click option that automatically places an initials field on every page
Can we have the one-click option that automatically places an initials field on every page
1 vote -
Remove the "unlimited per month" label on the Stripe checkout page
Rename "unlimited" to something like "ongoing" or "subscription" in the Stripe metadata passed to Stripe.
1 vote -
Dynamic Payment Amount Based on Signing Date
Allow payment amounts in PandaDoc documents or forms to be automatically adjusted based on the date a recipient signs (completes) the document.
1 vote -
Dynamic Payment Amount Based on Signing Date
Allow payment amounts in PandaDoc documents or forms to be automatically adjusted based on the date a recipient signs (completes) the document.
1 vote -
Attach quote as a PDF, when quote is sent
Please add an option to attach a PDF copy of the quote to the email PandaDoc sends recipients. Currently the email only links to the dynamic quote. Many customers prefer a PDF they can save, forward. Ideally a toggle at the template/workspace level.
Not just attachment on completion.
6 votes -
Support Referencing PandaDoc Catalog Items in Quote Builder via API
Support adding PandaDoc Catalog items directly to Quote Builder through the API using a Catalog identifier (e.g., SKU or Product ID), instead of requiring all product data to be passed inline in the payload.
2 votes -
Restrict editing while letting field update in generated documents.
Restrict users from editing the template structure (text, blocks, allowed content) while still letting them update field data in generated documents, without granting them edit access to the template itself.
1 vote -
Combine approval + first signer step
Problem: When the final approver is also the first signer, they can’t sign until after a rep sends the document, creating delays and extra handoffs.
Request: Allow an approver who is also a recipient in the signing flow to approve and complete their signature in the same action, or allow post-approval pre-signing before external send.
Value: Faster turnaround, fewer internal steps, clearer accountability.
Acceptance criteria: Optional toggle at template/workflow level; audit trail records both approval and signature events.
1 vote -
Bulk action for catalog items - Remove custom fields
Ability to remove all custom fields at once on multiple catalog items
1 vote -
Hide the name and email address of secondary signer when hover
When Signer 1 is signing a document with defined signing order, hover text showing Signer 2's info appears on disabled fields; customer requests a way to hide this hover text for privacy.
1 vote -
Reusable Conditional Content Sections & Centralized Rule Management
Enterprise customers need a reusable rule/content architecture for Smart Content and conditional template logic.
Today:
- Conditional content rules live only inside individual templates
- Rules cannot be centrally managed or reused globally
- Updating business logic requires manually editing many templates
- Content blocks can be reused, but the governance of the logic itself cannot
This creates major operational pain around:
- template maintenance
- rule duplication
- template drift
- scaling RevOps operations
- governance consistency across teams
Desired functionality:
- reusable conditional content sections/pages
- shared rule libraries
- “define once, reuse everywhere” architecture
- centralized rule management
- global updates across templates
- reusable smart content modules with embedded logic
- template…
1 vote -
Bundle Documents within Content Library, feature to Replace Source File within Templates, Transfer from Content Library to Templates
Currently, bundling documents can only be done for documents in Templates. However, the individual documents found in Templates can't be updated easily with "Replace Source File." This feature is only available in Content Library.
Updating various documents to be bundled together in Templates requires that I have the documents as Content Library items to perform any updates. Using "Replace Source File" allows me to keep any fields that were created rather than having to create them all over again or copying and pasting. Once it's updated as a Content Library item, I have to create a new Template with the…
1 vote -
Support HubSpot graduated tier pricing
Current HubSpot integration does not Support graduated tier pricing - products are passing to the pricing table/quote builder but the price do not.
2 votes -
Org-level API endpoint to retrieve workspace membership by user
Customer is requesting improvements to multi-workspace API architecture for Enterprise franchise use cases.
Current customer environment:
40+ franchise offices
Each franchise requires its own PandaDoc workspace
Users may belong to multiple workspaces
CRM + embedded signing workflow is the primary use case
PandaDoc is being used primarily as an API-driven signing/orchestration layerCurrent pain points:
Workspace API keys are isolated per workspace
Customer must maintain:
workspace API keys
workspace/user mappings
webhook management per workspace
synchronization logic internally
No efficient org-level way to dynamically determine which workspaces a specific user belongs toMain customer request:
Org-level API endpoint to retrieve workspace…
1 vote -
UPDATE CERTAIN PIPEDRIVE FIELDS
I have seen that it is possible to update fields in Pipedrive through variables present in a document. Although there is no way at the moment, to decide WHICH varibles (and so CRM fields) to update, leaving the others unchanged.
1 vote
- Don't see your idea?