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

2995 results found

  1. 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)
  2. 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)
    Not Planned  ·  Alessio Ragni responded

    Hi there,

    Thanks for sharing this idea. At the moment, this is not on our roadmap, mainly because the use case isn't fully clear to us yet.

    Currently, line items or products are pulled in and used as inputs for our quoting components — like the pricing table or quote builder. We're not planning any changes here for now.

    That said, if you have a specific scenario or workflow in mind, we’d really love to hear it! Feel free to reply here or drop me an email — happy to follow up and see if this is something we should explore further.

  3. 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)
  4. 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)
  5. 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  ·  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)
  6. We would like to request the implementation of proactive expiration notifications for Microsoft OAuth client secrets connected to PandaDoc business email settings. Specifically:

    Advance Warning Emails — Notify the account owner and/or admin via email when a connected Microsoft client secret is approaching its expiration date (e.g., 30 days, 14 days, and 7 days before expiration).
    In-App Notification — Surface a warning banner or notification within Settings > Business Email when the connected token is nearing expiration.
    Post-Expiration Alert — If the token has already expired, immediately notify the account owner so they can take action before document delivery is…

    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)
  7. In the new document creation experience, the "Setup Payment" step appears in the workflow for every document — even when payment collection is globally disabled at the workspace level. This forces users to click through an irrelevant step every time they create a document, adding unnecessary friction to their workflow.

    Expected behavior:
    If payments are disabled globally in workspace settings, the "Setup Payment" step should not appear in the document creation flow at all. It should only be visible when payments are enabled.

    Additional context:

    Users who previously relied on a streamlined document creation → generate link flow now require…

    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)
  8. Have Claude MCP integration with EU Server

    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. I want a Copilot integration

    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. Ability to replicate the "Replace source file" process on the Mobile App.

    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)
  11. With Templates, a secondary signer can decline to sign and leave a comment explaining what needs updating. This removes the signature but retains all other fillable form field values, allowing the original signer to revise and re-sign without having to repopulate the entire form from scratch. Please implement the same functionality for Forms.

    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)
  12. Have the ability to build conditional logic at the template level so when documents are sent to clients the correct information can be collected based off of their selection vs using a form. For example if a client selects option A inside of a document then upload documents appear vs option B a text block would appear.

    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)
  13. Similar to other CRMs

    When Contract is signed push info to Attio -> Deal stage shifts

    Choose Assignee from Contacts in Attio.

    Set economic buyer to deal for the people record, that is with the mail address.

    No overlay in attio, if documents are linked.

    Super pain was to come over form old crm to attio -> Pandadoc still has zoho id, but these cannot be changed to attio deal ids to use it in the integration.

    and further more.

    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)
  14. The automation that attaches documents to the HubSpot deal record only attaches the completed PandaDoc document as a PDF. Files that recipients upload within a document (via a file upload field) are not automatically synced to HubSpot as separate attachments — this is a current limitation of the External Automations add-on.

    Unfortunately, there's no native way within PandaDoc to automatically push uploaded files to the HubSpot deal record at this time. The uploaded files would need to be manually downloaded from the PandaDoc document and added to HubSpot separately.

    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. Example use cases:
    - A pop-up to users who try to modify a template with a note that they're changing a prepared template
    - A flag to users who try to create a field in a document to capture Credit Card information

    Business outcomes:
    - Reduces business users going rogue and modifying pre-approved template language
    - Prevents users from capturing credit card information since PandaDoc itself is not PCI-compliant

    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)
  16. Set within a theme the ability to choose a fill-in color to match branding for the account. At the moment, fill color isn't able to be saved to a theme requiring manual adjustment each time using the HEX code.

    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. Ability to bundle a document to another after the document has been published. This is incredibly useful when we have multiple pieces of paperwork that come together in a contract and we want them all housed in one document.

    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)
  18. Add Cost Subtotal / Total Cost to Quote Builder Footer

    Quote Builder currently allows users to track Cost at the individual line-item level, but there is no option to display the total Cost across all line items in the Quote Builder footer.

    Please add Total Cost / Cost Subtotal as an available footer calculation, similar to Subtotal, Total Quantity, Discounts, Fees, and Taxes.

    Use case

    For businesses that use Quote Builder for margin-aware pricing, the total selling price alone doesn't provide enough information to make pricing decisions.

    Our sales team uses the Cost field to track internal and pass-through…

    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)
  19. The Ref. Number associated with a signed document only appears on the Certificate of Signature. The reference number should also appear somewhere on the signed document (preference top left portion of page 1 at a minimum). There are many instances where the certificate is not desired to be a part of a final document so the signed document must be saved with the certificate, pdf printed and the certificate stripped from the document. When this is done there is no identifier remaining on the document to connect with the certificate for future reference.

    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. The number of pages for a Certificate of Signature from a signing process is too large. Reduce the image size of the signature and placement of recipient verification to get a minimum of 3 signers/page.

    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)
  • Don't see your idea?