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

3784 results found

  1. Ability to use an existing form on the Collect Form Data in Workflows.

    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 →
  2. We would like to offer bank transfer as a payment method using Stripe as the payment gateway. A workaround where customers transfer funds directly to our account isn't very practical because we can't automate the process that way. Please make bank transfer available (alongside SEPA and credit card).

    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

  3. Summary:
    When using PandaDoc's Salesforce integration, customers are unable to carry over native Salesforce product Groups into their PandaDoc documents. Groups exist at the Salesforce UI level but there is currently no mechanism to pass them through to PandaDoc automatically.

    Desired Behavior:
    When a document is generated from a Salesforce Opportunity, PandaDoc should automatically recognize and reflect the product Group structure. organizing line items into their respective groups as sections within 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

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

    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 →
  5. 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

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

    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

  7. Looking for an automation triggered three days prior to proposal expiration, which sends a reminder email with original proposal for review.

    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

    1 comment  ·  Automations  ·  Admin →
  8. Would like to have the option to enable this when navigating document lists, statuses, etc. (outside of Editor)

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

    1. Update every example on that page to curly braces.
    2. 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

    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 →
    • 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

    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 →
  10. 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

    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. Turn off field auto-snap permanently

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

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

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

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

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

    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. Since the recent changes, our workspace users are now able to add, delete and move fillable fields when sending templates. They CANNOT be allowed to do this. It creates major problems including potential legal issues. We need to be able to turn off/remove this option for our users.

    rephrasing: As an Enterprise admin, I need to prevent my workspace users (non-admin members) from adding, moving, or deleting fillable fields when creating documents from shared templates. Our documents contain legally-sensitive field placements and unauthorized field modifications create compliance and legal risks. Content Locking currently does not protect fields (by design). We…

    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. Allow the ability to add a 0 zero quantity to a quote from CRM

    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. Provide a Wrapper in template builder that converts a plain text token passed through to the Template into HTML (hubspot Rich Text field support)

    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