5657 results found
-
2 votes
-
2 votes
-
Copper Sync - Refresh Document
Customer doesn't want to generate a NEW document if he made changes to details in his Cooper account. Wants the existing document to adapt to the new changes
2 votes -
Move Checkbox
Ability to adjust were the optional checkbox falls in a pricing table
2 votes -
Unchecked boxes disappear once sent to client
Make the check boxes options that are not "checked" from the sender's side disappear once the document is sent to the client.
2 votes -
2 votes
-
2 votes
-
2 votes
-
Accept Button before signing
Button accept before signing the document from the clients' side.
2 votes -
2 votes
-
api revision number as token
api revision number token for document changes
2 votes -
2 votes
-
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 -
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 -
Naming Conventions
It would be great if the final, completed document signed by customers could be saved as a different file name than the template name.
For example, the Template Name is Pacific Solar Contract - [Deal.DealName] because it is customer facing, but when the final, signed PDF is downladed to our server, we would like to name the file yyyy-mm-dd - [Deal.DealName], Signed Contract (with the date being the completed date).
1 vote -
Dynamic Payment Processing Fees by Payment Method
Is there a way to pass through payment processing fees to the customer based on their selected payment method?
Currently, I apply a flat 3% “Credit Card Fee” to invoices, but bank transfer/ACH processing fees are actually lower. I’d like to offer customers multiple payment options while only charging the applicable processing fee for the method they choose, rather than charging ACH/bank transfer customers the higher credit card rate.
Ideally, this would:
Automatically adjust the fee based on payment method
Clearly display the fee breakdown to the customer
Allow lower-cost payment methods like ACH/bank transfer to have reduced fees
Still…
1 vote
- Don't see your idea?