3784 results found

1. API endpoint to delete a single Collect Files upload without deleting the whole document

   There's currently no API endpoint to remove just a Collect Files field's uploaded file from a Completed document — the only option is deleting the entire document via the API, which also removes its PDF, certificate, and audit trail. Customers using Collect Files for identity verification need a way to purge just that file after a retention period (e.g., 180 days) while keeping the document itself intact.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →

2. AI Content Detection & Automatic Approval Workflow

   As AI-generated content becomes increasingly common in sales proposals, organisations need governance to ensure customer-facing documents are accurate, compliant and on-brand before they are sent.

   We would like PandaDoc to automatically detect AI-generated text and images within a proposal and trigger a configurable approval workflow.

   Business case
   Many organisations encourage the use of AI to improve productivity, but AI-generated content can introduce risks including:

   Incorrect branding and logos
   Inaccurate product or technical claims
   Misleading AI-generated images or diagrams
   Over-promising functionality
   Legal, compliance and reputational risk

   Rather than preventing AI use, PandaDoc should help organisations govern it.

   Expected behaviour
   When AI-generated content is detected:

   Flag the document before it can be sent.
   Display which pages or sections contain AI-generated content.
   Allow administrators to configure approval rules (e.g. Marketing, Product Manager or Sales Manager approval).
   Record an audit trail showing AI-generated content was reviewed and approved.
   Allow thresholds such as "AI content detected" or "More than 25% AI-generated" to trigger approvals.

   This would help organisations confidently adopt AI while maintaining quality, consistency and compliance for customer-facing proposals.

   As AI-generated content becomes increasingly common in sales proposals, organisations need governance to ensure customer-facing documents are accurate, compliant and on-brand before they are sent.

   We would like PandaDoc to automatically detect AI-generated text and images within a proposal and trigger a configurable approval workflow.

   Business case
   Many organisations encourage the use of AI to improve productivity, but AI-generated content can introduce risks including:

   Incorrect branding and logos
   Inaccurate product or technical claims
   Misleading AI-generated images or diagrams
   Over-promising functionality
   Legal, compliance and reputational risk

   Rather than preventing AI use, PandaDoc should help organisations govern it.

   Expected behaviour
   When AI-generated… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Approvals  ·  Delete…  ·  Admin →

3. Support IdP Group Sync & Group-Based Workspace Assignment via SCIM

   Enable SCIM group object provisioning and support dynamic workspace, role, and license assignment in PandaDoc based on IdP group membership (Okta, Entra, or other SAML/SCIM providers).

   10 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Settings, Workspaces & User Roles  ·  Delete…  ·  Admin →

4. Allow updating contract metadata via API for imported/completed documents

   We bulk-imported our legacy contracts into PandaDoc's Contract Repository and need to add metadata (partner, start date, end date, etc.) to them in bulk via API, so our team can search, filter, and report on this data. Right now this can only be done manually, one document at a time, through the editor's Data panel. Please add API support for writing Contract Repository metadata fields on documents, including ones that are already completed, so bulk-imported contract archives can be populated without manual data entry.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →

5. Pull Data Deal Stage - Ability to customize fields to help with selection.

   Under new editor, when selecting deal record from drop down in workflow step, would like ability to customize the fields that re displayed when selecting the deal record to attached to the document. Specifically, they want to include the deal stage.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations - HubSpot  ·  Delete…  ·  Admin →

6. Fix API text rendering to prevent text overlap with invisible field tags

   Problem:

   When PDFs with invisible (white-colored) embedded text containing PandaDoc Field Tags are uploaded via the API, the form text gets cut off or overlaid by the field tags. The same PDFs upload correctly via the UI with no text issues.

   Customer Impact: Forms created through the API are incomplete and unusable for signing—critical information is hidden.

   Feature request: Fix the API's PDF text rendering to match the UI behavior—ensure invisible field tags don't cause text overlap regardless of upload method.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →

7. New Editor: Negative padding support removed, reducing custom design capabilities

   he new PandaDoc editor no longer supports negative padding on content blocks such as images and text boxes. This was a key design capability they relied on and was one of their primary reasons for choosing PandaDoc.
   Specific request: restore negative padding support in the new editor experience before the Q3 full rollout.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Sharing & Collaboration  ·  Delete…  ·  Admin →
   Released  ·  AdminDaria Serebriakova (Product Ops Specialist, PandaDoc) responded

   Hi,

   Thank you for taking the time to leave your request. We have great news – the feature you requested is already available. For more information, please click the link below!

   Text block — Change block background and margins

8. Allow internal users on Member role to add documents to rooms they are a member of

   Internal users on a Member role should be able to add documents to rooms they have been added to, without needing to grant higher-level permissions that would give them visibility across all rooms in the workspace.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Rooms  ·  Delete…  ·  Admin →

9. Remove "per month" terminology on template level

   When generating a document that uses monthly recurring billing, it adds the term "per month" next to the price. We want the ability to adjust the template to prevent that from being added once the document is generated

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations  ·  Delete…  ·  Admin →

10. Filter reports by paid date

    I want to filter reports by the paid date, not the creation or completion date.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Documents & Data Management  ·  Delete…  ·  Admin →

11. Add Linked-Objects Support to MCP Connector

    The REST API supports linking documents to Salesforce Opportunities, but the MCP connector doesn't expose this tool.

    What customer needs: Ability to link API-created documents to Salesforce Opportunities so they appear on the Opportunity record and sync their status. Need to add linked-objects endpoint to MCP connector with provider, entitytype, and entityid parameters.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →

12. Support Secondary Templates as a Source for Conditional Smart Content

    Customers using Conditional Smart Content with multi-page or complex addendum sections are currently required to save each page or block to the Content Library individually. This creates a significant maintenance burden — any update to the addendum must be replicated across multiple library items manually.

    Requested Enhancement:
    Allow a full template or template section to be referenced as the conditional content source within a Smart Content block, rather than requiring content to be saved as static Content Library snapshots.

    Use Case:
    This customer uses a guided selling workflow with a three-option checkbox (UCaaS, CCaaS, CloudCare). When CloudCare is selected, a multi-page addendum section should appear in the Statement of Work. Today, this requires saving the addendum page by page into the Content Library and maintaining each item separately. If the addendum template ever changes, every saved library block must be updated individually.

    With secondary template support, the customer could point the conditional rule at a living template section that updates in one place — eliminating duplicate maintenance.

    Expected Behavior:
    - In the Smart Content block's Conditional tab, users can choose between a Content Library item OR a template (or template section) as the content to display when conditions are met.
    - Changes made to the referenced template section propagate automatically to any document using that conditional rule.

    Business Impact:
    - Reduces friction for Enterprise customers building complex, multi-section SOWs or proposal documents.
    - Addresses a core limitation of the current Content Library snapshot model for conditional content.
    - Supports more scalable template management for accounts with frequently updated addenda or legal sections.

    Customers using Conditional Smart Content with multi-page or complex addendum sections are currently required to save each page or block to the Content Library individually. This creates a significant maintenance burden — any update to the addendum must be replicated across multiple library items manually.

    Requested Enhancement:
    Allow a full template or template section to be referenced as the conditional content source within a Smart Content block, rather than requiring content to be saved as static Content Library snapshots.

    Use Case:
    This customer uses a guided selling workflow with a three-option checkbox (UCaaS, CCaaS, CloudCare). When CloudCare is selected, a… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Content Editing & Design  ·  Delete…  ·  Admin →

13. Native Salesforce Package — Support Total/Bottom-Line Discount Sync to Opportunity Line Items

    Currently, the native PandaDoc Salesforce package only captures line-item level discounts when syncing quote data back to Salesforce Opportunity Line Items. When reps apply a total or bottom-line discount (e.g. a reseller discount row added at the bottom of a channel quote), that discount is not captured in the sync — resulting in incorrect amounts on the Opportunity Line Item.

    There is also no native normalization between discount types, meaning a dollar-value discount can sync as a percentage (e.g. a $700 discount syncing as 700%), causing further data integrity issues downstream.

    Real-world impact:

    Affects channel quotes where reseller discounts are applied as a total bottom-line line item
    Results in incorrect Opportunity Line Item values in Salesforce
    Blocks accurate downstream reporting on discount behavior across the sales team
    Forces customers to build custom triggers/parsers in Salesforce to work around the limitation
    Complicates invoicing flows when Salesforce is used as the bridge to billing systems (e.g. NetSuite, QuickBooks)

    Requested enhancement:

    Extend the native sync to capture total/bottom-line discount rows from PandaDoc quotes
    Add native normalization so dollar and percentage discounts are correctly interpreted before syncing to Salesforce
    Ideally, allow customers to map how total discounts are distributed across line items on the Salesforce side

    Workarounds currently in use:

    Applying discounts at the line-item level instead (changes rep behavior)
    Constraining Discount column to percentage-only formatting
    Using middleware (e.g. Soligo) to normalize values pre-sync
    Building custom Salesforce triggers to parse PandaDoc document data independently

    Currently, the native PandaDoc Salesforce package only captures line-item level discounts when syncing quote data back to Salesforce Opportunity Line Items. When reps apply a total or bottom-line discount (e.g. a reseller discount row added at the bottom of a channel quote), that discount is not captured in the sync — resulting in incorrect amounts on the Opportunity Line Item.

    There is also no native normalization between discount types, meaning a dollar-value discount can sync as a percentage (e.g. a $700 discount syncing as 700%), causing further data integrity issues downstream.

    Real-world impact:

    Affects channel quotes where reseller discounts are… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →

14. Clio integration

    Native integration with Clio.com

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Delete…  ·  Admin →

15. Make conditional smart content visible or at least identifiable on the template

    Currently, when we add smart content from the content library, it leaves a placeholder saying "Content auto-populates here based on [x] variable". That note is useful, but it's not useful that we can't see the content. I understand that if there are a few a long pieces of content that may be selected, it makes the template really long. But it would be great if we could toggle on/off a preview of the content in each placeholder so we can remember/visualize what's supposed to be there. At the very least, it should have the name of the content library items that were selected to display in that block.

    Currently, when we add smart content from the content library, it leaves a placeholder saying "Content auto-populates here based on [x] variable". That note is useful, but it's not useful that we can't see the content. I understand that if there are a few a long pieces of content that may be selected, it makes the template really long. But it would be great if we could toggle on/off a preview of the content in each placeholder so we can remember/visualize what's supposed to be there. At the very least, it should have the name of the content library items… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Usability Improvements  ·  Delete…  ·  Admin →

16. Allow removal of bullet/number from a list item while retaining its indent alignment

    When building documents with numbered or bulleted lists, users frequently need to add continuation paragraphs beneath a list item — sub-paragraphs that visually align with where the list item's text begins, but without displaying any bullet or number marker.

    Current behavior:
    The editor offers two unsatisfactory options:

    Using the Indent button — creates an indented paragraph but does not match the text-start position of the list item above it, resulting in a visible misalignment
    Adding a list item — aligns correctly, but always shows a bullet, number, or symbol which is inappropriate in formal documents

    The only available workaround is manually inserting spaces or pressing Enter between lines and using the spacebar to approximate alignment — an imprecise, time-consuming process that produces inconsistent results across different screen sizes or PDF exports.

    Requested behavior:
    Add a way to remove the list marker (bullet/number/symbol) from a list item while preserving its indentation level. This would allow users to create cleanly aligned continuation paragraphs under numbered clauses without the marker appearing in the final document. This could be implemented as:

    • A "no marker" option in the list style picker
    • A dedicated "continuation paragraph" indent style that snaps to the text-start position of the preceding list item
    • OR: a toggle to hide the marker visually while keeping the indent

    Impact:
    This is particularly important for legal contracts, compliance documents, policy agreements, and any formal document where numbered clauses are standard. Users currently face a choice between misaligned text or unwanted markers — both of which undermine the professional appearance of the document. A clean hanging indent for continuation paragraphs is a fundamental word-processing capability expected in a professional document editor.

    When building documents with numbered or bulleted lists, users frequently need to add continuation paragraphs beneath a list item — sub-paragraphs that visually align with where the list item's text begins, but without displaying any bullet or number marker.

    Current behavior:
    The editor offers two unsatisfactory options:

    Using the Indent button — creates an indented paragraph but does not match the text-start position of the list item above it, resulting in a visible misalignment
    Adding a list item — aligns correctly, but always shows a bullet, number, or symbol which is inappropriate in formal documents

    The only available workaround is… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Content Editing & Design  ·  Delete…  ·  Admin →

17. Claude MCP integration with EU Server

    Have Claude MCP integration with EU Server

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integrations  ·  Delete…  ·  Admin →

18. Prefill the date field with document creation date

    Hi Team,

    There is an option to automatically fill the date field with the signing date but not an option to automatically fill the date field with the document creation date.

    I'd like to see that introduced as an option.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Fillable Fields & Variables  ·  Delete…  ·  Admin →

19. Add catalog images to the pricing table via API

    I want to add the products in a table that can then be selected or deselected but I want the catalogue images to be populated in there

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →

20. Unified Contract Dashboard & Management for External/Received Documents

    User Problem / Scenario:

    Users who frequently sign contracts created by external parties (where they are the recipient/signer) have no reliable, centralized way to organize, search, or track these documents long-term. Currently:

    • External documents disappear from the Home page view after 1 year.

    • Users cannot apply folders, tags, or status labels to external documents.

    • There is no filtered view to isolate "Documents Received / Signed" vs. "Documents Sent / Owned."

    • This creates a high risk of lost contracts and forces users to rely on error-prone manual PDF downloads.

    Proposed Solution:

    1. Persistent Access: Allow external documents to remain visible in the account beyond the 1-year mark.

    2. Organization Tools for Recipients: Enable recipients to apply tags/labels, custom notes, and folders to external documents within their own view.

    3. Dedicated View/Filter: Add a tab or filter on the Home page/Document List specifically for "External Documents" or "Signed by Me."

    User Problem / Scenario:

    Users who frequently sign contracts created by external parties (where they are the recipient/signer) have no reliable, centralized way to organize, search, or track these documents long-term. Currently:

    • External documents disappear from the Home page view after 1 year.

    • Users cannot apply folders, tags, or status labels to external documents.

    • There is no filtered view to isolate "Documents Received / Signed" vs. "Documents Sent / Owned."

    • This creates a high risk of lost contracts and forces users to rely on error-prone manual PDF downloads.

    Proposed Solution:

    1. Persistent Access: Allow external documents to remain visible in the… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Documents & Data Management  ·  Delete…  ·  Admin →