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

2912 results found

  1. 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. 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)
  3. In the classic editor, we could add or remove payment on a per-document basis directly from the right-hand panel. This gave us the flexibility to decide at the time of creating a document whether payment collection was needed — without having to go back and modify the template every time.

    Since the new editor rollout (Project Delta), payment is now controlled exclusively at the template workflow level. If a template has a "Collect Payment" step, every document created from it is forced through that step with no way to skip or remove it on the fly.

    This is a significant…

    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  ·  Workflows  ·  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. Comment from customer:

    I am planning to create a PandaDoc workspace named Internal and wanted to know if it's possible to configure a rule or policy that restricts document recipients to specific email domains.

    For this workspace, I would like to ensure that documents can only be sent to users with our internal email domain, @siebert.com. Is there a native setting or recommended approach to enforce this restriction?

    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. Unpublish multiple forms at once

    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  ·  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)
  6. 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)
  7. 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)
  8. fully-designed template page to be generated once per Opportunity Product when a document is created from Salesforce. Each generated page should render that product's own field values in a rich layout — in this case, a [Notes] placeholder populated from the Notes field of the corresponding Opportunity Product. The number of products is variable per Opportunity (for multiple opportunities)

    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)
  9. Enable us to push completed orders from PandaDoc directly to Rillet for invoicing.

    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. The ability to modify the scaling on a document. i.e when using a scanner, having the ability to modify dimensions from the document level vs from the scanner itself i.e Xerox.

    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. Function that would allow customers to detect Room activity via the API and connect it to their CRM data.

    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)
  12. As AI-generated content becomes increasingly common in sales proposals, organisations need governance to ensure customer-facing documents are accurate, compliant and on-brand before they are sent.

    We would like PandaDoc to automatically detect AI-generated text and images within a proposal and trigger a configurable approval workflow.

    Business case
    Many organisations encourage the use of AI to improve productivity, but AI-generated content can introduce risks including:

    Incorrect branding and logos
    Inaccurate product or technical claims
    Misleading AI-generated images or diagrams
    Over-promising functionality
    Legal, compliance and reputational risk

    Rather than preventing AI use, PandaDoc should help organisations govern it.

    Expected behaviour
    When AI-generated…

    3 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

    1 comment  ·  Approvals  ·  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. At the moment, when a product is left unselected in the PandaDoc pricing table or quote builder, it is automatically removed in the Opportunity Products.
    A feature request is to introduce the possibility of syncing both selected and unselected products back to the opportunity.
    The implementation can look like this: Either removing unselected products or syncing with QTY = 0 back to Salesforce, and to control that from PandaDoc Setting page

    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. Change Deal Stage in Pipedrive once document is sent/viewed

    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)
  15. Currently, when changes are made to Salesforce object schemas (such as field renames, new custom fields, or mapping updates), or when fields simply need to be resynced, administrators must manually open every single template in a workspace to refresh or update the Salesforce tokens/fields. For workspaces with dozens or hundreds of templates, this manual process is incredibly tedious, prone to human error, and a major operational bottleneck.

    Proposed Solution
    We need a way to trigger a bulk refresh of Salesforce field mappings for all templates within a specific workspace simultaneously. This could be achieved via two proposed methods:

    Option A…

    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)
  16. The ability to use a phone number (E.164 format) in place of an email address in the recipient field of the POST /documents/{id}/session endpoint.

    Currently, the endpoint only accepts an email address.

    For cases where recipients have no email address on file and the app handles the signing experience directly.

    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)
  17. Drawn signatures appear too light/gray on iPad during embedded signing — please allow opacity/pen thickness adjustment.

    Please add the ability to adjust the darkness/opacity (or ideally offer a black, solid-stroke option) for drawn signatures in embedded signing — either as a workspace setting, a document-level configuration, or an API parameter in the signing session configuration. This would significantly improve the signing experience for iPad users and ensure consistent, professional-looking signatures across all devices.

    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)
  18. On the Home screen or Document summary screen, it displays "Waiting Approval" - I want to see which approver it is waiting on.

    We have 3-4 approvers to ensure quotes are going out correctly, and for auditing purposes. Seeing this would be especially helpful for the approvers to quickly scan which documents need THEIR approval. It's also helpful for our sales reps to see who is holding up the process for an internal nudge, and admin if one of the approvers is OOO.

    Possible Solution: Add a column to the either (or both) screens: "waiting on" with approver's name.

    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  ·  Approvals  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. We have a Shopify website that allows customers to upload a reference image showing how they would like their product to be customized.

    As the contract is generated automatically through the API without any manual intervention, we would like this uploaded reference image to be displayed in the pricing table. Including the image would provide clear visual context for the customized product and help avoid any ambiguity.

    In scenarios where a customer uploads a reference image, our system creates a custom product via the API. However, we are currently facing a limitation in assigning the uploaded image to the custom…

    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)
  20. The data does not seem to line up correctly e.g. the contract term variable is 36 months in Hubspot, but in Pandadoc it automatically pulls in 3 years. We want to make sure the terminology is consistent across our documents.

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