Skip to main content

    603 Ideas

    newtoclmDigital Collaborator

    Authenticaton Settings for RecipientsParked

    I just found out today that if a recipient forwards the email that they receive with the link to the envelope and they already opened and authenticated their access using and Access Code, then the person that they sent the link to can open the document and basically just sign it as the first person.  This seems risky to me.  Also, the Authentication Settings for the Access Code feature basically do not allow for a person to require an access code for each new browser.  Basically, its either every single time or only once - no in between.  So all someone who is being nefarious would need to do is wait until you look at your document, allow you to enter your access code and then - boom, they’re in signing as if they were you with no record on the certificate.https://support.docusign.com/s/document-item?language=en_US&bundleId=pik1583277475390&topicId=muh1583277327950.html&_LANG=enusPer the Authentication Settings, "When using Access Codes with this setting, the recipient is not prompted to authenticate again after the first time, even if using a different device."I would like to suggest that this be changed in light of the forwarding issue, to allow for this to be switched to allow for the same as Phone Authentication, SMS Authentication, and Knowledge-Based ID checks. It should be allowable to require the access code every time they log in from a different browser. Like in the setting "Any recipient must authenticate on every envelope sent from this account"

    add disable "send later" for backButtonAction for send viewParked

    we check the sender view document:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createsender/for backButtonAction there are only previousPage and Redirect. We have set it to redirect, but there are still have “send later” button. when the  sender click ‘send later’, we send the envelope by API will failed.we create the send view url and the backButtonAction as redirect, then open the url in another browser tab.then click “send later”it will send envelope failed as before, we create case with support team. now it can send success.and we can query the scheduled workflow.because as customer request, the envelope need send without send later, so we need call delete the workflow api to remove the schedule. So we hope we can disable this option for this button. and another requirement is there are two signer, it will throw error place at least one field per recipient when click send later. but the customer want add requirement in the parameters of creadSend API like backButtonAction. let the sender must drag at least one signature for each signer. now we need query the recipient tabs and check whether each signer has signHereTabs and dateSignedTabs before send envelpe. we hope it can check when click continue, if not drag should notice the sender drag it. as the customer told the sender always only drag one signer, but not drag others.