Skip to content

Ideas to Improve PandaDoc

💡 To help us understand (and hopefully implement!) your suggestion, please answer these few questions as you propose your idea:
  • What specific actions or behaviors do you expect from this feature?
  • What is the issue that this functionality would address for you? Why would you require it?

Ideas to Improve PandaDoc

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

2996 results found

  1. A standalone document-level status indicator that clearly shows when one of multiple signers has signed and the document is awaiting the remaining signature(s) — visible without needing to open the Audit Trail or the Recipients section.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Customers need a way to export, download, or otherwise extract comments and suggestions (including resolved and declined ones) from a document into a separate file or format, without granting the recipient direct access to the original document as a collaborator.

    Current limitations:

    1. There is no way to download or export comments and suggestions
    2. Declined suggestions cannot be restored, only accepted ones via version history
    3. The only visibility option (View > Resolved comments and suggestions) is restricted to the document owner
    4. The only workaround is adding the other party as a collaborator with "Can view and comment" permissions, which some customers…
    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. We bulk-imported our legacy contracts into PandaDoc's Contract Repository and need to add metadata (partner, start date, end date, etc.) to them in bulk via API, so our team can search, filter, and report on this data. Right now this can only be done manually, one document at a time, through the editor's Data panel. Please add API support for writing Contract Repository metadata fields on documents, including ones that are already completed, so bulk-imported contract archives can be populated without manual data entry.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Under new editor, when selecting deal record from drop down in workflow step, would like ability to customize the fields that re displayed when selecting the deal record to attached to the document. Specifically, they want to include the deal stage.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. PandaDoc's PayPal integration only supports credit card payments, not ACH, which is essential for large transactions.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Problem:

    When PDFs with invisible (white-colored) embedded text containing PandaDoc Field Tags are uploaded via the API, the form text gets cut off or overlaid by the field tags. The same PDFs upload correctly via the UI with no text issues.

    Customer Impact: Forms created through the API are incomplete and unusable for signing—critical information is hidden.

    Feature request: Fix the API's PDF text rendering to match the UI behavior—ensure invisible field tags don't cause text overlap regardless of upload method.

    Requested by Client: jthibodeau@bwalk.com (Ticket for reference: 126471189)

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Internal users on a Member role should be able to add documents to rooms they have been added to, without needing to grant higher-level permissions that would give them visibility across all rooms in the workspace.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Rooms  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Ability to define fixed, automatic PDF page breaks in templates so printed offers come out correctly without manually adding Page break blocks.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. When a user copies a field with a configured HubSpot merge field mapping from one template to another, the merge field configuration is lost. The field itself transfers, but the merge field data source and property mapping must be manually reconfigured in the new template.

    This requires users to re-do field setup work when reusing fields across templates, especially problematic for teams that standardize field configurations across multiple templates (e.g., copying a "Deal Amount" field mapped to HubSpot's amount property).

    Expected: Merge field mapping should persist when the field is copied to a new template, just as other field properties…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Have IP Addresses listed for view documents, not just completed documents.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. The REST API supports linking documents to Salesforce Opportunities, but the MCP connector doesn't expose this tool.

    What customer needs: Ability to link API-created documents to Salesforce Opportunities so they appear on the Opportunity record and sync their status. Need to add linked-objects endpoint to MCP connector with provider, entitytype, and entityid parameters.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Description:

    Currently, Smart Forms display all fields on a single page. There is a customer need for the ability to create multi-step web forms where users progress through sequential pages using a "Continue" or "Next" button, with each step containing a subset of fields.

    Use Case:
    Customers are looking to replicate step-through form experiences from other providers. Typical workflows require:

    Step 1: Collect owner information
    Step 2: Collect additional details
    Step 3: Final confirmation
    etc.

    Requested Requirements:

    Support multiple pages/steps within a single Smart Form
    Navigation buttons (Continue/Next, Previous/Back) between steps

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Forms  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Customers using Conditional Smart Content with multi-page or complex addendum sections are currently required to save each page or block to the Content Library individually. This creates a significant maintenance burden — any update to the addendum must be replicated across multiple library items manually.

    Requested Enhancement:
    Allow a full template or template section to be referenced as the conditional content source within a Smart Content block, rather than requiring content to be saved as static Content Library snapshots.

    Use Case:
    This customer uses a guided selling workflow with a three-option checkbox (UCaaS, CCaaS, CloudCare). When CloudCare is selected, a…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. The checkbox in word document cannot be shown as checked when docx is imported in PandaDoc. As the selection of word document will affect the signature, it would be great if an enhancement of word editing can be made.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. When docs are about to expire if there is a way we can have an auto extend one more week for all docs that are about to expire rather than having to push out individually?

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Automations  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Currently, there is no native way in PandaDoc to bulk-export the data that recipients fill into the fillable fields of completed documents as a CSV file. Fillable fields such as text fields, date fields, and dropdown fields that recipients complete when signing a document are not captured in any existing report or export option. Users who send the same template to multiple recipients need to be able to compile all of that recipient-entered data in fillable fields, such as name, address, and phone number, into a single downloadable CSV file across all completed documents from that template.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Currently, the native PandaDoc Salesforce package only captures line-item level discounts when syncing quote data back to Salesforce Opportunity Line Items. When reps apply a total or bottom-line discount (e.g. a reseller discount row added at the bottom of a channel quote), that discount is not captured in the sync — resulting in incorrect amounts on the Opportunity Line Item.

    There is also no native normalization between discount types, meaning a dollar-value discount can sync as a percentage (e.g. a $700 discount syncing as 700%), causing further data integrity issues downstream.

    Real-world impact:

    Affects channel quotes where reseller discounts are…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Native integration with Clio.com

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Request to have a granular permission layer for pricing tables and content blocks that would allow document owners or template admins to:

    Lock the structural placement of a table or content block — preventing it from being moved, resized, or deleted by the document sender or recipient.

    Allow selective field interaction within that locked block — enabling reps to see and select drop-down options, enter values in designated fields, and fill in required information without risking accidental layout changes.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Ability to enable In person signing on Account Level so newly created workspaces would adapt the setup.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 … 149 150
  • Don't see your idea?