3784 results found
-
Turn off field auto-snap permanently
Turn off field auto-snap permanently
1 vote -
New Editor: Negative padding support removed, reducing custom design capabilities
he new PandaDoc editor no longer supports negative padding on content blocks such as images and text boxes. This was a key design capability they relied on and was one of their primary reasons for choosing PandaDoc.
Specific request: restore negative padding support in the new editor experience before the Q3 full rollout.2 votesHi,
Thank you for taking the time to leave your request. We have great news – the feature you requested is already available. For more information, please click the link below!
-
Pin/Split-View for Document Arrangement & Signature Boxes
The UI uses tabs for "Document arrangement" (left) and "Signature boxes" (right). When you click one tab, the other disappears, forcing constant toggling.
Request: Add a "pin" button that allows both tabs to be visible side-by-side simultaneously (split-view).
1 vote -
Multi-Signer Field Management - UI
Problem: When preparing a document with multiple signers (e.g., 2 clients + sender = 3 signers), users must toggle/switch between signers repeatedly to place signature, date, and initial boxes. This requires excessive clicking.
Request:
Option A: Show all signer fields (signature, date, initial boxes) for all signers on the same screen simultaneously
Option B: Add keyboard shortcuts to jump between signers quickly
1 vote -
extend recipient view audit log to include all views, not just the first
extend recipient view audit log to include all views, not just the first
this would be required for a security access audit on the document, controls need to exist to show details about every view
2 votes -
add audit trail entries for internal users that access/open a document
add audit trail entries for internal users that access/open a document
even after a document is signed, for security access control audits
2 votes -
in the document details endpoint, for each recipient, add the number of views that recipient has had on the underlying document
in the document details endpoint, for each recipient, add the number of views that recipient has had on the underlying document
2 votes -
Save payment method to Stripe customer for future charges when a one-time payment is completed
When a client completes a one-time payment through the payment step, their card is not saved to the Stripe customer record. The only way to keep a card on file is the separate Card details field, which forces clients to enter their card twice in the same document. Awkward, redundant labor. Please add an option (with a client consent checkbox at checkout) to save the payment method to the Stripe customer record during a one-time payment, so merchants can run later approved charges like post-event adjustments without a second card entry. Stripe already supports this natively through setupfutureusage…
1 vote -
Options to change the approvers in "Approval Stage"
Organizations with complex signature policies (e.g., Legal review determining if Finance, Compliance, or Executive approval is needed) require the ability to route documents to different approvers based on content reviewed during the initial approval step, rather than having all downstream approvers locked in at template creation.
Current Limitation: Once a document enters the "To approve" stage, the approval workflow is locked. Approvers cannot be added, removed, or changed, they must all be predetermined in the template.
2 votes -
Tracking Rejection Reasons in PandaDoc
When a document is rejected in an approval workflow, PandaDoc currently only allows a free-text comment as feedback. While helpful, this makes it very difficult to track, categorize, and report on rejection trends at scale.
What we're requesting:
A mandatory or optional dropdown field that appears when an approver rejects a document, allowing them to select a predefined rejection reason category (e.g., "Rep Error," "Missing Information," "System Issue," "Pricing Error," etc.) before the rejection is submitted. Ideally this would be configurable per workspace or template so teams can define their own categories.The ideal outcome:
Approvers select a rejection reason…
2 votes -
Show expiration date as a column in the document list and search results.
When searching for a proposal from a specific person, the expiration date should be visible directly in the document list or search results.
Expected behavior:
Add an “Expiration date” column in the document list and in search results so users can quickly identify documents by their expiration date.
Current limitations:
The expiration date is not currently visible as a column in the document list or search results.1 vote -
Notary Session Remiders
Ability to send reminders to recipients for on demand notary sessions.
2 votes -
Manage approval workflow emails and notifications via API
There should be a way to manage the approval notifications and emails to document's approvers when the documents are sent via API.
2 votes -
Variables in document name should resolve in system-generated notification emails
When a document is sent to a recipient, PandaDoc automatically generates a notification email that includes the line "[Sender] sent you [Document Name]." This line pulls the document title directly and cannot be edited or customized.
When the document title contains a variable (e.g. [Client.Company] Agreement), the variable appears as a raw, unresolved token in the recipient's email notification instead of the actual value. This looks unprofessional to recipients and undermines the purpose of using template-level variables for standardized document naming conventions.
Use case: We use variables in the document name at the template level to maintain a consistent naming…
1 vote -
Automatic $ to % Discount Normalization for Salesforce Sync
When syncing PandaDoc pricing tables/quote builders to Salesforce Opportunity Products, discount format mismatches ($ vs %) cause sync failures or incorrect data mapping.
PandaDoc allows line items to accept both flat-amount ($) and percentage (%) discounts, but the Update Opportunity Products trigger syncs discount values as-is without format normalization. If a line item has a $ discount and the mapped Salesforce field expects %, the sync breaks or writes the wrong value.
Goal: Automatically normalize all discounts to percentage format during SFDC sync, so:
- If a line item has a $ discount, convert it to the equivalent %
-…2 votes -
Quote Builder: Display Values in Parentheses
Add support for displaying values in parentheses in the Quote Builder.
Example: Discount ($200).2 votes -
Ability to prevent workspace users from adding, moving, or deleting fillable fields during document creation
Since the recent changes, our workspace users are now able to add, delete and move fillable fields when sending templates. They CANNOT be allowed to do this. It creates major problems including potential legal issues. We need to be able to turn off/remove this option for our users.
rephrasing: As an Enterprise admin, I need to prevent my workspace users (non-admin members) from adding, moving, or deleting fillable fields when creating documents from shared templates. Our documents contain legally-sensitive field placements and unauthorized field modifications create compliance and legal risks. Content Locking currently does not protect fields (by design). We…
1 vote -
Section-scoped token values when building document bundles via API
When using the sections/uploads endpoint to build a bundled document from multiple templates, token (variable) values passed in the second call are applied globally across the entire document - overwriting same-named token values from the first call.
Fields already support section-level scoping via the mergefieldscope=upload query parameter, but tokens do not. This creates a hard limitation for dynamic bundling use cases where templates are selected at runtime (e.g. from CRM data) and cannot be pre-configured with unique token names per bundle combination.
The current workaround — converting shared tokens to fields and using mergefieldscope=upload - requires…
2 votes -
Restrict the ability to change the document sender
The ability to restrict users from changing the document sender.
2 votes -
Document.Value on pandadoc__PandaDocDocument__c object in Salesforce
The customer would like to see Document.Value as a field on pandadocPandaDocDocumentc object in Salesforce.
5 votes
