Skip to content

Ideas to Improve PandaDoc

💡 Your PandaDoc ideas are getting a better home!
We appreciate all the feedback you’ve shared with our Product Team. This forum is now read-only as we've migrating to the new PandaDoc Community. Don't worry—your existing ideas and votes will come with us!
Join the PandaDoc Community and submit your ideas here.

Ideas to Improve PandaDoc

Categories

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

295 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

  2. Sync Collect Files field in Dropbox

    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

  3. 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

  4. 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

  5. Allow recipients to upload files when filling out a Form

    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

  6. Right now, we can only have one price field come over from CRM, would like to have two, as we quote two different ways, sometimes we like to define the discount as a lump sum, and sometimes we like to do it as a line item discount. We can't have two different templates now as the data variable only comes over after the document is generated (would like to avoid requiring the user to add a column to the table as they don't always know which one is correct.)

    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

    Hi. We aren’t planning on building this into our feature set at this point in time since it doesn’t fit into our current product roadmap. Please keep upvoting this idea so we can keep considering it every time we work on our roadmap.

    Should you come across any other ideas that suit your business needs, don’t hesitate to give them an upvote!

  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

    Hi. We aren’t planning on building this into our feature set at this point in time since it doesn’t fit into our current product roadmap. Please keep upvoting this idea so we can keep considering it every time we work on our roadmap.

    Should you come across any other ideas that suit your business needs, don’t hesitate to give them an upvote!

  8. 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

  9. Description: System variables (e.g. company address, sender details) always display in English regardless of the Recipient View Language setting. These values should respect the configured language so that all content — including variable-populated fields — is presented consistently in the recipient's language.

    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

  10. Users need the ability to include a variable in a document template that can be populated via CSV during Bulk Send but remains invisible to recipients. The primary use case is embedding internal tracking identifiers (e.g., workflow tags, custom IDs) for retrieval via the API — without exposing that data in the recipient-facing document. Current workaround is setting the variable's font color to white, which is fragile and unsupported. A native hidden/metadata field option would eliminate this friction.

    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

  11. I would like the ability to set a timeframe in which a client can sign their document, such as no sooner than 30 days before the expiration date. Our process specifically requires their signature to be within 30 days of the planned service date for legality. We would like clients to be able to see and review the document before then, but not allow them to sign it until a specific timeframe. Rather than fill in a data manually, we would like to select something like expiration date minus 30 days as the soonest signing date so that it auto-calculates…

    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

  12. What’s the problem?

    There’s currently no way to resize multiple fields at once in the document editor. Users must manually resize each field individually, which is time-consuming when working with forms that have many fields.

    What we need:

    The ability to select multiple fields and resize them all to the same dimensions in one action.

    Why it matters:

    Saves significant time when building forms and templates
    Creates consistent, professional-looking documents
    Reduces repetitive manual work
    Current workaround:

    Resize one field, then duplicate it—but this doesn’t help when fields already exist and need to be standardized.

    This version is concise and gets…

    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

  13. Feature Request:
    Add the ability to save and reuse individual standard fields (such as Name and Job Title) as standalone items that can be quickly inserted into any document, especially when working with different uploaded PDFs.

    Problem It Solves:
    Currently, when users work with different PDFs each time, they must manually recreate common fields like “Name” and “Job Title” for every new document. There’s no way to save these standard fields as reusable items outside of templates or content library blocks.

    How It Should Work:
    Users should be able to save individual fields (e.g., “Name” text field, “Job Title” text…

    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

  14. Problem Summary
    Currently, PandaDoc assigns all fields to roles on the template. If a field is unassigned when you send the document, PandaDoc will auto-assign it to a signer, making it editable by the client recipient—even if you intended it to be internal-only and “read only” for external signers. There’s no intuitive way, in the UI or API, to assign a field to an internal/non-signer, fill it pre-send, and then have it locked for the client who is the only signer. This results in a loss of control and integrity for fields intended as internal-use or immutable after preparation.

    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

  15. Date fields (or any field type) should not be resizable smaller than the minimum required to display the data. It does not make sense that I can add a date field, but size it small enough that I can't actually read the date. If the field requires entering the day, month, and year to the field, I should not be able to de-size the field to the point that I can't see part of that date.

    Otherwise, if there are use-cases where de-sizing it and obstructing the field is useful, there should be a lock/unlock option on fields so you…

    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

  16. Option to have "Agree" field that would count as a signature (in case there is no signature field in the 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

  17. Integrate with JetPay payment gateway

    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

  18. Ability or option not to automatically change the fields names on template and document bundling.

    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

  19. eg - CompanyName (field) pre-populates with Company.Name (variable) and variable updates when field changes.

    PandaDoc's "AI" bot tool gives the below instructions (which are wrong) to do this. But it would be great if this actually worked.

    --
    Yes, you can create a field in your PandaDoc template that prepopulates with the Company.Name variable and allows the client to edit it, updating the variable throughout the document. Here's how:
    In your template, go to the Variables tab and find the Company.Name variable.
    Copy the variable name without square brackets.
    Click on a field in your template and select 'Properties' on…

    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

  20. Option to prefill a field that the signer still has to confirm is correct and prompt them to do so. Required fields that are prefilled with information by the Sender are being skipped over as "answered".

    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