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

176 results found

  1. 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 →
  2. Currently, reporting and CSV exports include statuses like Draft, Sent, Viewed, Completed, Expired, and Declined, but there is no way to see a global count of documents that were rejected in the approval workflow.

    “Rejected” exists as a document status in the API, but it is not available in reporting dashboards or exported analytics files.

    Request: Add a Rejected status tile in reporting and include it in the CSV export so teams can track this metric across all 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  ·  API  ·  Admin →
  3. When I select 'preview' on a form under the templates tab, it creates a new form, which is then deducted from my usage credits -- this is deceptive, as a preview shouldn't create a new form. A preview -- by description -- is supposed to show you what the page will look like when active, but not be active itself.
    The usage credits are very expensive, so you need to warn people in advance that you can't preview a form without creating one, and that it will cost you a credit. I've wasted a bunch of credits on this, when…

    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 →
  4. 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 →
  5. 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 →
  6. Ability to add a slide show of multiple images in a 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

    0 comments  ·  API  ·  Admin →
  7. Customer is requesting improvements to multi-workspace API architecture for Enterprise franchise use cases.

    Current customer environment:

    40+ franchise offices
    Each franchise requires its own PandaDoc workspace
    Users may belong to multiple workspaces
    CRM + embedded signing workflow is the primary use case
    PandaDoc is being used primarily as an API-driven signing/orchestration layer

    Current pain points:

    Workspace API keys are isolated per workspace
    Customer must maintain:
    workspace API keys
    workspace/user mappings
    webhook management per workspace
    synchronization logic internally
    No efficient org-level way to dynamically determine which workspaces a specific user belongs to

    Main customer request:

    Org-level API endpoint to retrieve workspace…

    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 →
  8. Create an API endpoint or webhook that triggers based on individual field completion or real-time page navigation.

    we're looking for some way of better tracking how far along someone's getting with a document. Right now it's split into 10 key requirements, so we thought maybe that's a better way of tracking progress within a 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

    0 comments  ·  API  ·  Admin →
  9. It would be great to have the ability to filter webhook history in the PandaDoc Developer Center using a custom date range, in addition to the existing preset options. This feature would make it easier to review and analyze webhook events for specific periods.

    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 →
  10. A notification or prompt that the APIK key needs to be reset if the user who generated is removed.

    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 →
  11. Client/prospect needs to set radio buttons as optional when creating documents from file upload using field tags
    Currently, the * optional modifier works for textfield, checkbox, dropdown, signature, date, and initials field tags (e.g., {textfield*____}), but not for radio buttons

    Radio buttons use a different syntax ({{radio:role:optId}}) and don't support the optional modifier

    This forces manual configuration after document creation, which doesn't work for automated workflows

    Request to add optional modifier support to radio button field tags for consistency with other field types

    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 →
  12. Today, the Redirect URL after completion setting appears to be static. It would be extremely valuable if this redirect could be dynamically customized per document/session via integrations (e.g., Make / Zapier) or via variables, so customers can redirect signers to different landing pages and pass custom query parameters.

    Why this matters (use case):

    We run multiple campaigns and need to send signers to different LPs depending on:

    document template / campaign

    recipient / segment

    region / language

    deal owner / pipeline stage

    We also want to pass tracking parameters such as:

    utmsource, utmcampaign, utm_content

    internal IDs like doc…

    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 →
  13. In Team Dashboard when you select a name and pull up the metrics for the team member, then go into one of the options (ie View) and when you click the back button it does not take you back to the team member dashboad but the Team Dashboad as a whole. Sounds like this is something that PandaDoc has not thought of having a back option so it takes you back to where you last were and not from the start which is not efficient

    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 →
  14. HubSpot requires Record ID's to be ingested as NUMBER type data.

    PandaDoc currently sends custom Webhooks with a "linked_objects" header in the JSON payload, but this is a STRING.

    When building a Custom Event or Webhook Receiver in a HubSpot Workflow, the build attempt will always fail because it cannot parse the STRING or coerce it to NUMBER, and results in a failure to finalize the webhook.

    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 →
  15. Ability to add a logo to a custom app from the Dev Center.

    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 →
  16. Option to see the number of API usage I have in a month and in a year. Break it down by workspace and 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

    0 comments  ·  API  ·  Admin →
  17. I was wondering if the webhooks can detected dupilcated documents, I am trying to track when a duplicated documents and make a workflow and when I complete a duplicated document it doesn't seem to pick it up when I test the webhook.

    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 →
  18. Issue:
    Currently, when adding a new Recipient Group through the PandaDoc API (or manually) with the exact same name as an existing group, the existing group's members are overwritten or updated with the new group's members, instead of creating a distinct new group.

    Impact:
    This behavior causes significant issues and data inconsistencies, particularly when managing recipient groups programmatically via the API, as it leads to unintended changes in existing recipient lists.

    Proposed Idea/Solution:
    Please implement a system that ensures recipient groups with identical names are treated as separate and distinct entities. This could be achieved by:

    Automatically appending a unique…

    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 →
  19. 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 →
  20. Introducing filters for returns for users, members, and workspaces would allow us to get these things by individual instead of having to sort a list on our side.

    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 →