Skip to main content
arrow-left Back to Docusign.com

Featured topics

How to Use the Ideas Feature

What you need to know about Docusign Community IdeasThis guide will walk you through the process of sharing your ideas, voting on existing ideas, and...

Update on the status of submitted ideas

Hi everyone! We’ve heard your questions about the status of submitted ideas in the Ideas forum.Internally, the Docusign team is actively reviewing you...

    Filter by Idea status

    Filter by category

    1017 Ideas

    S
    Newcomer
    Set default behavior for multiNewcomer

    Set default behavior for multiple documents in a Salesforce Docusign Gen template to uncheckedExisting Functionality

    When a Docusign Gen template with multiple documents is used, all documents are selected by default. This makes it very time-consuming for users to deselect all the documents not needed. As document rules are very limited in terms of only fields of the record can be selected and also only the conditions "equals" and "Not equals" can be used, this would make life much easier and would safe a lot of time for our users.

    2
    M
    Forum|Forum|6 months ago
    A
    New Voice
    ANDRANew Voice

    REPORT ON " WAITING ON OTHERS"Idea Submitted

    A basic compliance report that shows me who i am waiting on for a signature. Docusign is massive , huge but this is a basic compliance report that you dont have.I have 42 people that i am waiting on , i need a report that gives me these people that I need to email and chase to sign. Thanks.

    0
    A
    New Voice
    Forum|Forum|6 months ago
    W
    Newcomer
    WAC RyanNewcomer

    Allow sender generated Access Codes to be an accepted "Authenticate" method.Idea Submitted

    I believe that years ago the Access Code would count as a valid authentication method when the security settings are configured to "Any recipient must authenticate on every envelope sent from this account". At times we have recipients who cannot recive our required SMS text for authentication. We would like to be able to use the Acces Code as an authetication method. But when the customized Access Code option is chosen by the sender and the policy is set to "Any recipient must authenticate on every envelope sent from this account" the the recipiant must still authenticate by SMS text or knowledge based methods after entering the sender provided Access Code.Thus I request prgraming be modified to allow sender generated Access Codes to be an accepted "Authenticate" method - or allow the Admin to add this as an option to authenticate. Authentication SettingsRecipient Authentication SettingsRecipient Authentication SettingsAny recipient must authenticate on every envelope sent from this account  

    0
    W
    Newcomer
    Forum|Forum|6 months ago
    K
    Newcomer
    kirm2Newcomer

    Shared Access Enhancement - Allow SharePoint Integration to Open Shared AccessIdea Submitted

    When integrating DocuSign into SharePoint, there is an option to move the document to DocuSign to setup signatures, unfortunately there is no way to use Shared Access with this feature. Enable API call to open DocuSign into the Shared Access group (so if you have multiple shared access groups you can enable it to the specific group the user will need based on the folder/site they are in).

    0
    K
    Newcomer
    Forum|Forum|6 months ago
    T
    Newcomer
    TravieNewcomer

    We need the Ability to Combine multiple Gen templates to avoid Large template issues in SaleforceParked

    The more fields added to a Gen Template the harder it is to manage. There are multiple “Wait” and “Reload” on the Add Fields Tab. IF we had the ability to combine multiple templates into one using the same or different Objects it would be more efficient and easier to manage. 

    2
    M
    Forum|Forum|6 months ago
    A
    Active Voice
    AkshayActive Voice

    To add the ability of using the PDF form field transformation functionality via our DAL integrationExisting Functionality

    When we upload a document from Salesforce (DAL Integration) to DocuSign, there are multiple dynamic editable form fields that are present in the document but after it gets uploaded to the docusign, the form fields are misaligned and doesn’t work as expected. As per DocuSign(case #15506376 ) the form field data conversion functionality is designed to work only when a document is uploaded directly into the DocuSign tagger page (Prepare and Send in Salesforce). This behavior does not apply when sending a PDF from Salesforce.As the step to detect form fields in the rasterizer, which is triggered on an upload into Docusign directly, is not used when sending over a PDF from Salesforce, it is expected behavior at this point that form fields are not recognized as per DocuSign. We are expecting that the  form field data conversion functionality works when uploading/sending a PDF from salesforce directly. the alternative resolution to this are not usable for our business need. this should be available through enhancement at DocuSign end.

    2
    M
    Forum|Forum|6 months ago
    L
    New Voice
    LauraCNew Voice

    Admin access to download the Email LogIdea Submitted

    Ability to run a report that will retrieve all the emails sent by the system (notifications, reminders, etc.) within a period of time. This report should include the envelope ID, the sender, recipient, date and time, status. Such report can be a powerful tool for admins to investigate issues related to missing or duplicate notifications.

    0
    L
    New Voice
    Forum|Forum|6 months ago
    J
    Active Voice
    JmaierVTAActive Voice

    Recipient Attachment Rotation OptionsParked

    When external customers utilize Powerforms or Webforms, they can attach files via the attachment field, but they have no basic controls after file attachment.  I believe that document rotation tools would be a very beneficial tool (short of some automated orientation feature, which may not always be accurate).Once a recipient attaches their documents, they are unable to rotate them.  Sometimes customers need to attach supporting documentation but for one reason or another, they’re scanned in an incorrect orientation (e.g. 90 degrees).  Giving them the ability to rotate their attached document would help where we have end-to-end automated processes (e.g. post-completion tasks via Agreement Actions to send to a read only CMS).

    2
    J
    Forum|Forum|6 months ago
    L
    Active Voice
    Longstride00Active Voice

    Auto Attach PDF on the new Envelope Status (DocuSign Status)Parked

    When creating a DocuSign Envelope on the Legacy version, the PDF files, Notes & Attachments automatically get connected to the DocuSign record (dsfs__DocuSign_Status__c). This does not happen for the new DocuSign Status (dfsle__EnvelopeStatus__c). Can we have the old feature applied on the new feature?Old feature: New feature:  

    2
    M
    Forum|Forum|6 months ago
    Hengfeng Ge
    Hero
    Hengfeng GeHero

    about disable the button 'send later ' in send viewParked

    Hello Ideas team,We advice all of our customer migrate to new send view as this document told:https://www.docusign.com/blog/developers/esignature-rest-api-embedded-correct-view-updated?msockid=13eac2ad5d496fc10dc3d62c5c416ee9and also can find the document:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createsender/we find the setting as below:{ "returnUrl": "<url>", // URL required "viewAccess": "envelope", // required "settings": { "startingScreen": "Prepare", // (default) or "Tagger" "sendButtonAction": "send", // (default), "redirect" "showBackButton": "true", // (default), "false" "backButtonAction": "previousPage", // (default), "redirect" "showHeaderActions": "true", // (default), "false" "showDiscardAction": "true", // (default), "false" "lockToken": token_value, "recipientSettings": { "showEditRecipients": "true", // (default), "false" "showContactsList": "true" // (default), "false" }, "documentSettings": { "showEditDocuments": "true", // (def,ault), "false" "showEditDocumentVisibility": "true" // (default), "false" "showEditPages": "true", // (default), "false" }, "taggerSettings": { "paletteSections": "default", // (default), "none", "custom" "paletteDefault": "custom" // "merge", "notary", "seals", // "smartContracts", "annotations", // "smartSections" } } }}Now the customer want disable the send later button. maybe can a parameter like showSendLaterButton, default is true, and can change it to false. so the send later button can hide. becuase they embedded this view in their system, the workflow is control by their system, so no need send later. Now some people may make a mistake, and the process can't go down, stop, and have to modify and increase the workload.  thanksFreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024📊 DocuSign Community Leaderboard Top 5 contributor🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng/

    3
    niani.byrd
    Forum|Forum|6 months ago
    J
    New Voice
    johnhaveman3New Voice

    Notification When Someone Has SignedDuplicate

    I receive notifications when someone views a document, but not when they have actually signed.Given the name of the app, DocuSIGN, this seems to be a giant oversight.Please can we have a notification where someone SIGNS.This has been covered elsewhere in the community, but seems to be ignored.Thank you! 

    1
    M
    Forum|Forum|6 months ago
    Scott.Nieman
    Troubleshooter
    Scott.NiemanTroubleshooter

    Use HTTP Status Codes in e-Signature the way they are intended for Level Two RESTful MaturityParked

    We have a big problem with e-Signature APIs. They do NOT report error properly in a RESTful manner.  We should NEVER have silent failures where the HTTP status response code states a happy 200 status, but the response body contains an error message.  This is an anti-pattern, as we should never be forced to introspect a response body to look for errors and throw our own exceptions. We should be catching these as errors as either 4xx or 5xxx series errors.The renowned Martin Fowler provides a nice Reader’s Digest condensed version of Richardson’s Maturity Model.From https://martinfowler.com/articles/richardsonMaturityModel.html#level2“There is another difference if something goes wrong, such as someone else booking the session.HTTP/1.1 409 Conflict[various headers]The important part of this response is the use of an HTTP response code to indicate something has gone wrong. In this case a 409 seems a good choice to indicate that someone else has already updated the resource in an incompatible way. Rather than using a return code of 200 but including an error response, at level 2 we explicitly use some kind of error response like this. It's up to the protocol designer to decide what codes to use, but there should be a non-2xx response if an error crops up. Level 2 introduces using HTTP verbs and HTTP response codes.”

    8
    niani.byrd
    Forum|Forum|6 months ago
    R
    New Voice
    rollervidesNew Voice

    Do not reorder my recipients for meParked

    Hi,For QA purposes the signing order of recipients for my documents usually doesn’t matter. However, when docusign automatically reorders my recipients without my knowledge or consent, it confuses me because i am usually referencing an ordered list. when the names are put out of order, it is more difficult for me to verify that i added all the needed recipients. let me change the order to what i want it to, then toggle off set signing order, but preserve the order i set just for my own view.

    5
    M
    Forum|Forum|6 months ago
    R
    Newcomer
    rafallo5Newcomer

    KIR mSzafir one time signature introductionParked

    We would like to use the one time QES delivered by outside vendor (KIR) that is a TSP (Trust Service Provider) registered in Poland. It is because they deliver wide range of identity verification methods by Polish banks and goverment wallet. To do so I would to request addition of KIR to the following list: https://support.docusign.com/s/document-item?language=en_US&bundleId=xww1594245808169&topicId=iek1617724891136.html&_LANG=enus As a prework we do asked KIR if they are willing to build an integration to support our needs and they are open for cooperation.We also tried the current QES options within docusign specifically IDV and it is not meeting our requirements due to obligation to scan personal ID’s by phone etc which is not required with KIR and their identity verification by Polish banks etc.FYI, KIR website: www.kir.pl and specific QES that is KIR product: www.mszafir.pl

    2
    M
    Forum|Forum|6 months ago
    S
    Newcomer
    Scott BulmerNewcomer

    Add option for “Recipients Can Collaborate” on Attachments fieldParked

    When using a Template that contains the Attachment field, a user creates a document for esignature and uploads any kind of document to the attachment field. However, when the user then "Assign to Someone Else" the attachments that were uploaded do not carry over to the other user.There does not seem to be an option to “Collaborate” with the Attachments field.The end result would be that any attachments the first user uploads carry over and remain attached, so the second user can see them and does not have to re-attach.

    2
    M
    Forum|Forum|6 months ago
    CRod
    Conversation Starter
    CRodConversation Starter

    Ordinal Date Format for Date SignedParked

    I recently got asked how to setup the Date Signed field in an Ordinal Date format (e.g. 16th day of July in the year 2025).Right now, there isn’t a way to do this - I think it would require the Date Signed to be broken up into its three parts: Day (and correct ordinal - “1st”, “2nd”, “3rd”, “th”), Month, and Year.Is there any discussion of creating a Date Signed field that will allow this?

    3
    M
    Forum|Forum|6 months ago
    Z
    Conversation Starter
    Zainab OlawoyinConversation Starter

    Preserve Original Document Formatting in Agreement Template BuilderParked

    It would be highly beneficial for the Agreement Template Builder (ATB) to retain the original formatting of uploaded documents, similar to how the classic editor functions. Many of these documents follow a specific house style, and preserving formatting is essential for consistency and professionalism.Currently, the ATB struggles to maintain original formatting, which results in additional time and effort for users to manually correct layout and style issues. Enhancing this functionality would significantly improve user experience and efficiency when creating agreement templates. 

    2
    J
    Forum|Forum|6 months ago
    J
    New Voice
    j.brown7New Voice

    Allow templates to be created for Shared AccessParked

    Hello,We have a number of Shared Accounts in DocuSign and we are starting the process of getting users to utilize Shared Access rather than logging into the account.One question came up with how to access the templates they use under that account.  Right now there isn’t a way to access those templates, still just what is shared in a Shared Template folder or shared directly with an account.  It would be great to be able to access and create/delete templates for a Shared Account with the Shared Access feature rather than needing to use a folder or direct sharing.

    2
    J
    Forum|Forum|6 months ago
    K
    New Voice
    KeyRentalsNew Voice

    Need notifications to work properly to email us when a signer accesses a documentIdea Submitted

    We have 2 docusign accounts. One for real estate sales and the other for our property management company. We have the same notification preferences set for both accounts. The sales account ALWAYS send us an email when any signer first views their envelope. The property management account has NEVER sent us an email when a signer first views an envelope. After multiple back and forth troubleshooting sessions with support they cannot figure out why and suggested that we make an enhancement suggestion here. So that is what we are doing even though this is already a feature in DocuSign that works on one account and has never worked on our other account. Has anyone else experienced this type of issue?

    5
    M
    Forum|Forum|6 months ago
    S
    Newcomer
    Stephen LNewcomer

    Request for Enhancement - Copying Sentence Rules - InsightIdea Submitted

    RFE: enables copying sentence rules so we don't have to retype all of the keywords/exclusion words for the different variations with and without entities? Product: Docusign Insight

    0
    S
    Newcomer
    Forum|Forum|6 months ago
    C
    New Voice
    chrisrichardsukNew Voice

    Allow external reviewer to reassign reviewer to someone else in their organisationIdea Submitted

    It would be beneficial if the external reviewer who receives a document could reassign it to someone else at their organisation (typically their legal team).

    0
    C
    New Voice
    Forum|Forum|6 months ago
    R
    New Voice
    Rafi_mNew Voice

    New shared access feature flawIdea Submitted

    Dear DocuSign Team, We recently started using the DocuSign new shared access feature in our organization, migrating all the actual access from the old to the new feature. After that, I discovered that the new feature is designed to not allow users to access a shared envelope via a direct link, which caused a huge manual work for some of our departments.The answer I received for why the new feature was designed in that way was to: to prioritize security and control. However, this is not convincing.In any case, it would be awesome, if you can consider enabling the link access for the new feature, because right now we had to rollback and use the legacy feature. Thank you,Raafat

    0
    R
    New Voice
    Forum|Forum|6 months ago
    M
    Newcomer
    Miss KNewcomer

    Agreement Actions from DocuSign app launcher in SalesforceParked

    I noticed you do not have an out of the box way to send completed DocuSign documents to SharePoint from the DocuSign App Launcher in Salesforce. This will definitely improve your user experience and limit the use of another system integration to action this.

    2
    J
    Forum|Forum|6 months ago
    J
    New Voice
    JDAFSNew Voice

    Export Shared Access Settings within the OrganizationDuplicate

    We can export a list of users and memberships, but the CSV file lacks columns indicating shared access and its settings. While the Shared Access page is helpful for viewing individual users, it's impractical to audit permissions across the entire organization this way. To effectively review and manage shared access, we need the ability to export a comprehensive list—including users with shared access, permission levels, expiration dates, etc.—in a CSV format.

    1
    M
    Forum|Forum|6 months ago
    H
    Troubleshooter
    Han.ChenTroubleshooter

    A report for monitoring the usage of Shared AccessUnder review

    Could we have a report for admins to monitoring usage of the Shared Access for all users? This ideally should include: who's been sharing with whom, their permission level (Allow to manage/edit/send) and the duration of sharing.Currently we would need go into users one by one to view if they have any Shared Access set. And it’s just not possible to do if you have hundreds of DocuSign users.Thanks. 

    8
    M
    Forum|Forum|6 months ago

    Filter by category

    • All capabilities
    • All Capabilities

    Leaderboard

    Badges

    • 1st Question Posted
      goodrich4bkhas earned the badge 1st Question Posted
    • 1st Question Posted
      ame2026has earned the badge 1st Question Posted
    • 1st Question Posted
      MeganB88has earned the badge 1st Question Posted
    • 1st Reply Posted
      KatSaghas earned the badge 1st Reply Posted
    • 1st Question Posted
      Muhammad Alihas earned the badge 1st Question Posted
    Show All Badges
    Code of ConductAccessibility statement

    Docusign Community

    Code of Conduct