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. Visibility / colour
    The "Email templates" label sits in a very light grey on a white background, so it blends in and isn't obviously a clickable button. It's easy to miss that it's there at all. Could the default colour be made brighter / higher contrast so it's clear at a glance that it's a button I'm about to click?

    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

  2. When creating a document that the customer does not want to eSign and only wants a PDF of, allow for changing of the status from draft to Sent. Currently can only change from draft to Completed or Rejected.

    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. Ability to select left, center, or right alignment on an image placeholder so that images uploaded via API during document creation have the correct alignment. Currently, the alignment settings only appear once an image has already been placed in the placeholder.

    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. Currently, when a document has been signed and sent to the next recipient, the document stays in viewed status; however, we would like the status to change to something else so that we can see the document has been signed by one recipient, but not the other

    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. the ability to create bundled products via API

    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

    0 comments  ·  API  ·  Admin →
  6. Currently, the "Update Salesforce fields with PandaDoc field values" trigger is global, and write-back behavior can only be controlled by manually configuring Merge Field mappings on each template individually. There is no centralized way to define which templates should or should not participate in the write-back.

    Incase one has multiple templates, they need a template-level toggle or an allowlist/denylist in PandaDoc Setup to manage this at scale, without having to audit every template manually.

    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

  7. Ability to view who made what edits on a completed document. Essentially the Version History for a completed document

    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

  8. When a bundle document is signed, the recipientcompleted webhook returns pricing.tables[] with no reference to which section each table belongs to. The same gap exists in GET /documents/{id}/details. There's currently no way to cross-reference pricing tables back to their originating bundle section via the API.
    Request: Add a section
    uuid field to each pricing table object in:

    recipientcompleted webhook — pricing.tables[].sectionuuid
    GET /public/v1/documents/{id}/details — pricing.tables[].section_uuid

    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 →
  9. Allow payment amounts in PandaDoc documents or forms to be automatically adjusted based on the date a recipient signs (completes) the document.

    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

    1 comment  ·  Workflows  ·  Admin →
  10. I need the chat dialogue box it's critical. It was the deciding feature for us staying with Pandadoc. Docusign has this feature.

    6 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

  11. Currently, SSO group-based provisioning in PandaDoc only applies during the initial user creation at first login and does not update group assignments on subsequent logins for existing users. We would like to request the ability for SSO group-based provisioning to also apply to existing users on future logins, so that group membership and related access can be dynamically updated based on IdP group changes.

    This enhancement would ensure that user access remains aligned with identity provider group assignments over time, reduce manual administrative updates, and improve overall access management accuracy and security.

    6 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

  12. It would be good if it could include additional columns, such as workspace name and created date

    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

  13. When multiple documents with the same title are downloaded in bulk (documents are bulk uploaded), PandaDoc automatically adds numbers to the file names, which makes it difficult to distinguish between them. It would be helpful to include the recipient’s name in the document title instead.

    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

  14. Include the document type in webhook payload so that this can be used for automations and 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  ·  API  ·  Admin →
  15. Rooms: upload one document to multiple rooms 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  ·  Rooms  ·  Admin →
  16. The Certificate of Signature should also indicate whether the document signed by the recipient included any attachments at the time of signing. If attachments were present, the certificate must display the attachment's name and relevant details.
    This ensures full transparency for the recipient, confirming that any attachments were part of the original document from the start — and were not added after the signing was completed. This protects the recipient from unknowingly signing a document that may have had files appended without their knowledge.

    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

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

  18. Receive emails when an update for Salesforce is available

    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

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

  20. The ability to take a current workflow and copy it over into another workspace on the user end.

    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