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

7622 results found

  1. Because we have setup custom roles for each workspace (which works well so far) I have already seen there is no way to assign via the mapping rules a new user to multiple workspaces with different roles for each
    I can see that for a group name you can choose multiple workspaces to assign but they all need to apply the same role
    If I try to add more than one rule for the same group name with a different workspace/role then PandaDoc says group name already listed and cant save
    Not the end of the world but means if…

    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)
  2. Allow a single identity provider (IdP) group to be mapped to multiple PandaDoc workspaces with different roles during SSO provisioning. Currently, a group can only appear once in the mapping table and all assigned workspaces must use the same role. Enabling more flexible mapping logic would help organizations with multiple teams and workspaces automate provisioning more effectively.

    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)
  3. Hoping to have this feature on quote builder "to auto-hide the section when there are no products in it"

    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)
  4. At the moment, the "Template updated" webhook trigger includes the following events:

    Changes to template name
    Changes to template roles
    Addition of a section

    The feature request is to extend the “Template Updated” webhook trigger scope to cover updates to templates fields (or possibly introduce a separate trigger "Template updates (fields)".

    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)
  5. When a document is fully signed/completed, automatically apply a visible mark or stamp on every page (e.g., "Signed" or "Completed"). This gives viewers, recipients a clear, at-a-glance confirmation that the entire document is executed, regardless of which page they're viewing.

    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)
  6. Currently, when a document is declined in PandaDoc, selecting a decline reason is optional. Making decline reasons required would ensure that every declined document includes clear feedback. This improves data quality and eliminates situations where documents are rejected without context.

    Capturing structured decline reasons helps teams identify patterns such as pricing objections, contract terms, timing issues, or client concerns. With more consistent data, organizations can generate more reliable reports, refine their proposals, and improve overall close rates.

    Requiring a reason before allowing a document to be declined would strengthen accountability, provide actionable insights, and support better decision-making across sales and…

    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)
  7. Ability to hide certain pages from specific recipients when the completed file is downloaded.

    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. The Clipping Mask, uses a vector shape, and is placed on top of a image, to crop or mask the image, and the visual output will be whatever the vector shape is.

    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)
  9. Disable renewal + feature on a workspace level. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Currently there are no options to set text alignment for quote builder headers and columns (left/center/right) resulting in sloppy looking tables when presenting quotes to customers.

    Adding this feature would help with visual appeal and make both PandaDoc and our company appear as if we have an eye for detail.

    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. If the email specified in the sender parameter does not match an existing workspace user, PandaDoc may automatically assign the document to the default workspace sender. In PandaDoc, the document owner always takes precedence over the sender parameter if the sender does not match the document owner or meet workspace requirements. Even if your API call sets a different sender, the document will still be sent from the document owner.

    Would like this to not occur, and allow for the sender perimeter to set the sender email

    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  ·  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. In many workflows, at least one signer is always required (e.g., a company representative fills out information before the document goes to customers for signing). However, the number of customer signers can vary - sometimes there is only one, and other times there are two.

    Currently, if we mark Signer 2 as required, it creates a problem when there is no second signer. If we leave Signer 2 optional, the signature is not enforced when a second signer is present.

    Requested Behavior:
    - Signer 1 should always be required.
    - Signer 2 should be conditionally required:

    If a second signer…

    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  ·  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)
  13. Alternative to retrieve a signed document. Adding a version control to easily protect the singer and sender if a signed document accidentally edited.

    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)
  14. Automatically send the document for signature immediately after approval

    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)
  15. When a Folder is at the top level, both navigation and Document move/copy functionality are completely bricked. Major program defect. Documented in support Ticket #76173928: "Issue with Folder and Room Structure Affecting Document Copy and Move".

    Solution options:
    1. Prevent use of Folders at top level, require it must be Rooms.
    2. Make program navigation and document move/copy navigation work if Folders are at the top level.

    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)
  16. At this point, when you creating a document via bundling a few templates (that have signing order enabled), signing order is getting erased. The client would like to preserve it.

    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)
  17. Request for a new API endpoint that returns all workspaces associated with a specific user within an organization.

    Example desired functionality:

    GET /users/{user_id}/workspaces

    or

    GET /user-workspaces?user_id={id}

    This would allow integrators to dynamically determine which workspaces a user belongs to without retrieving the full user list across the organization.

    Customer Context

    Customer operates a franchise model with:

    40+ workspaces

    500+ users

    Shared identity across the organization

    Heavy API-based embedded document workflows

    Users may belong to multiple workspaces simultaneously.

    The customer initiates document creation from their CRM and needs to determine which workspace the user should interact with before creating 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

    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)
  18. Option to automatically hide the Total Contract Value in the quote builder totals section at the template level to avoid manual hiding in each generated document when pulling data through data merged in HubSpot.

    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)
  19. Requesting to have this feature back. Make it easy for users for content design.

    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)
  20. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 381 382
  • Don't see your idea?