226 results found
-
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 -
Section-scoped token values when building document bundles via API
When using the sections/uploads endpoint to build a bundled document from multiple templates, token (variable) values passed in the second call are applied globally across the entire document - overwriting same-named token values from the first call.
Fields already support section-level scoping via the mergefieldscope=upload query parameter, but tokens do not. This creates a hard limitation for dynamic bundling use cases where templates are selected at runtime (e.g. from CRM data) and cannot be pre-configured with unique token names per bundle combination.
The current workaround — converting shared tokens to fields and using mergefieldscope=upload - requires…
2 votes -
[Fillable Fields - Dropdown] Ability to add an option to a specific position in the list (i.e. Add below ) instead of at the bottom
Ability to add a dropdown option directly to a specific position (i.e. Add below an existing option) instead of at the bottom by default. Each existing item should have the option to add another item below it, instead of just the remove option.
2 votes -
Localize system variable values based on Recipient View Language
Description: System variables (e.g. company address, sender details) always display in English regardless of the Recipient View Language setting. These values should respect the configured language so that all content — including variable-populated fields — is presented consistently in the recipient's language.
1 vote -
Hidden Variables in Documents - CSV-Populated Field Not Visible to Recipients
Users need the ability to include a variable in a document template that can be populated via CSV during Bulk Send but remains invisible to recipients. The primary use case is embedding internal tracking identifiers (e.g., workflow tags, custom IDs) for retrieval via the API — without exposing that data in the recipient-facing document. Current workaround is setting the variable's font color to white, which is fragile and unsupported. A native hidden/metadata field option would eliminate this friction.
1 vote -
Do not sign before or set a window/timeframe to sign
I would like the ability to set a timeframe in which a client can sign their document, such as no sooner than 30 days before the expiration date. Our process specifically requires their signature to be within 30 days of the planned service date for legality. We would like clients to be able to see and review the document before then, but not allow them to sign it until a specific timeframe. Rather than fill in a data manually, we would like to select something like expiration date minus 30 days as the soonest signing date so that it auto-calculates…
1 vote -
Date Field: Font Type
Have the ability to change the font of the date field to match the document font.
2 votes -
Bulk Resize Multiple Fields to Equal Dimensions in Document Editor
What’s the problem?
There’s currently no way to resize multiple fields at once in the document editor. Users must manually resize each field individually, which is time-consuming when working with forms that have many fields.
What we need:
The ability to select multiple fields and resize them all to the same dimensions in one action.
Why it matters:
Saves significant time when building forms and templates
Creates consistent, professional-looking documents
Reduces repetitive manual work
Current workaround:Resize one field, then duplicate it—but this doesn’t help when fields already exist and need to be standardized.
This version is concise and gets…
1 vote -
Add Reusable Standard Fields (Name & Job Title) for Quick Insertion Across Documents
Feature Request:
Add the ability to save and reuse individual standard fields (such as Name and Job Title) as standalone items that can be quickly inserted into any document, especially when working with different uploaded PDFs.Problem It Solves:
Currently, when users work with different PDFs each time, they must manually recreate common fields like “Name” and “Job Title” for every new document. There’s no way to save these standard fields as reusable items outside of templates or content library blocks.How It Should Work:
Users should be able to save individual fields (e.g., “Name” text field, “Job Title” text…1 vote -
Assigning Fields to Internal Non-Signers
Problem Summary
Currently, PandaDoc assigns all fields to roles on the template. If a field is unassigned when you send the document, PandaDoc will auto-assign it to a signer, making it editable by the client recipient—even if you intended it to be internal-only and “read only” for external signers. There’s no intuitive way, in the UI or API, to assign a field to an internal/non-signer, fill it pre-send, and then have it locked for the client who is the only signer. This results in a loss of control and integrity for fields intended as internal-use or immutable after preparation.1 vote -
Ability to print signatures on paper documents
Ability to print signatures on paper documents and align with the formatting.
2 votes -
Autovalidation of minimum field size
Date fields (or any field type) should not be resizable smaller than the minimum required to display the data. It does not make sense that I can add a date field, but size it small enough that I can't actually read the date. If the field requires entering the day, month, and year to the field, I should not be able to de-size the field to the point that I can't see part of that date.
Otherwise, if there are use-cases where de-sizing it and obstructing the field is useful, there should be a lock/unlock option on fields so you…
1 vote -
Ability to include CRM variables into reports
Ability to include CRM variables as column options into reports
2 votes -
Checkbox field: Design and color options to make it more visible
Option to change checkbox colors from default gray to more vibrant, visible colors for better visibility and user experience.
3 votes -
Refresh feature to populate role variables of recipients after document was created
When a document is created without a recipient assigned to a role, the role variables remain empty. However, if a recipient is added later, they are not auto-filled with the information connected to that recipient.
2 votes -
Remove the locked in lines on the forms and change font size
Make the forms so that when placing the signature block on the page the signature doesn't lock into a random line that doesn't line up with actual signature line and change the default signature font size to 12 instead of 15 so it fits on most forms.
2 votes -
Issue with recipient groups when creating docs from templates
Fix issue with recipient groups so that they don't get deleted when starting a document from a template. When assigning roles there is a user field for recipient groups. It's a predefined group so there is no need to add a user, and when someone does by mistake, it clears the entire group from the document once created. This is critical for us as we have a contract distribution group for executed deals, and when the group gets cleared the users that need a copy don't receive.
3 votes -
System Variable for Document Renewal Date
Add a system variable that automatically populates the document renewal date.
2 votes -
Collect fiels field: setup file type
To select only certain file types that can be uploaded in forms. We want customers to only upload .doc files for example, not pdf or jpg
2 votes -
"Agree" field
Option to have "Agree" field that would count as a signature (in case there is no signature field in the document)
1 vote
- Don't see your idea?