2991 results found
-
Add an attribute to a href on career page
For instance takie this position applicaation https://www.pandadoc.com/careers/principal-product-manager-document-domain-eu/#main-content.
When user is finished with the application flow they see the block with info containing linktr.ee link that doesn't work properly everywhere as it is embedded.
I suggest changing the link to <a href="https://linktr.ee/pandadoc_recruitment" target="_blank">here</a> so it would open in the new tab.
1 vote -
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 -
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 -
expiration reminder
Looking for an automation triggered three days prior to proposal expiration, which sends a reminder email with original proposal for review.
1 vote -
Proposal expiration reminder automation
Looking for an automation triggered three days prior to proposal expiration, which sends a reminder email with original proposal for review.
1 vote -
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 -
MondayCRM
- 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 -
Workspace-level automatic CC recipients for document notifications
Ability to set specific email addresses at the workspace level that automatically receive document sent and completed notifications without appearing as CC recipients on the document itself. Right now the only way to notify additional people is by adding them as visible CC recipients per document or template, which adds extra steps and shows those addresses to our clients. We need a way to have internal stakeholders notified silently in the background, without affecting the recipient experience on the client's end.
1 vote -
Turn off field auto-snap permanently
Turn off field auto-snap permanently
1 vote -
Global setting to assign a CC recipient to all signed documents. (Workaround posted in comments)
Have the option to put a global setting for documents to have a default CC recipient. Or have the option to have a user be notified of documents that are signed even if they are not a recipient or CCd to the document.
1 vote -
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 -
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.
1 vote -
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 -
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
- Don't see your idea?