Back to Docusign.com
Here are some of the latest popular questions that developers asked on Docusign Community in the month of June 2025.
Thread: Hide finish later option popup when it appears on clicking of "Finish Later"
Summary: This developer wants to hide the popup that appears (as seen in the screenshot below) when a user clicks Finish Later while signing a document with Docusign.
Answer: This confirmation popup is a standard part of the Docusign signing process and can’t be disabled. However, it is possible to disable the Finish Later button entirely if you don’t want to give users that option. To do that, follow the steps below:
- Access Branding Settings: Navigate to the Brands section within Docusign eSignature Admin.
- Edit the Resource File: For the specific brand being used in the signing session, download the "Signing Resource File." This is an XML file that controls various text and UI elements.
- Modify the DocuSign_FinishLaterAllow Node: Open the XML file and locate the
<data name="DocuSign_FinishLaterAllow">node. By default, its value is true. To hide the button, change the value tofalseas demonstrated in the code below.<data name="DocuSign_FinishLaterAllow">false</data>
Thread: How to set prefill tabs when creating envelope from template
Summary: The developer is trying to set the values of prefilled tabs when creating an envelope from a template with the eSignature REST API. Although they are setting the value property on the tabs, the tabs are not being prefilled.
Answer: Prefilled tabs cannot be filled at envelope creation when the envelope is created using a template. To do this, you’ll need to create the envelope as a draft, and then update the prefilled tabs’ values using the EnvelopeDocumentTabs: update endpoint.
Thread: Use a single Docusign account for multiple users without requesting consent multiple times
Summary: The developer is setting up their Docusign developer account and they want it to be a dedicated account specifically created for API access. Their requirement is that “This account would be shared by all [their] users to send envelopes to recipients, both inside and outside [the] organization.” They’re facing some difficulties because they expect that they should only need to grant consent once, but they’re being asked to grant consent again every time they send an envelope from a new PC.
Answer: The best authentication type for the developer’s use case is JSON Web Token (JWT) Grant authentication. Currently, the developer is using Authorization Code Grant, which is why they are being asked for consent multiple times. With JWT Grant, consent will only be required once per integration key.