I have an document , which needs the signature from the developers account on default, how can I achieve this. I have successfully added a document and have generated the view url to be sent. But I want to add the signature of the developers account by default , cant seem to find a way to do this.
As Luis mentions in his comment above, it's not possible to automatically (programatically) add signatures to documents for some recipient(s) while requiring that other recipient(s) sign using DocuSign. You have a couple of options to get the developer's (i.e., sender's) signature on the documents:
Include the Developer (Sender) as the first recipient in the Envelope's workflow. (They'll sign using DocuSign, just as all other recipients will.) This is your best option, because you'll get all of the normal security and audit trail functionality that DocuSign provides for all signers.
Burn the Developer's (i.e., Sender's) signature into the document(s) prior to adding the documents to DocuSign. i.e., the signature will already be on the documents when you add them to DocuSign. Not a great option, IMO.
Keep in mind that automatically applying someone's signature to documents (i.e., either programatically or by burning the signature into the documents before adding them to DocuSign) somewhat nullifies the intended effect of a signature -- i.e., a signature typically implies one's agreement/consent -- but if the signature is applied without any action on behalf of the signer, then is agreement/consent truly in effect?
Related
I'm trying to find out if it is possible using the DocuSign API to create a signing request that is sent to multiple parties for signature with nobody seeing the other parties signatures until they have all signed?
Once all parties have signed I would download the final PDF and review this then send to all parties, but not sure if it's possible to hide these as it goes from one recipient to another?
Well, one technique would be for each signer to have their own signature page for the document set. The signature page would actually be a separate document within the envelope. (But signers are not particularly aware of the fact that there can be multiple documents in an envelope since they all flow together.)
You'd use the document visibility feature so each signer would only see the main document(s) and their own signing page.
Try it out first via the web tool, docs within the developer sandbox. Then automate via the API.
We are using REST API to create envelopes and the Template is set up in DocuSign, with signer roles etc. Our customer wants to be able to decide in every separate occasion whether to use InPerson signing or send the signing link via email to the recipient.
Currently/originally we implemented Embedded signing, but our customer wants the "security question" (e.g. ask for driver's license number) to be there before the signing. So that they can prove that the buyer has actually been there to sign.
Is there a way to do this? I have the DocuSign Template set up with "needs to sign" option, but when sending the request to create a new envelope, somehow change a signer to be InPerson and trigger a workflow for that?
I managed to find information about Embedded signing and clientUserId, but is there a way to deliver information for example to the Certificate of Completion, like with the InPerson case with the input showing there?
In order to switch from In-Person (embedded) to remote signing and vice-versa, you will need to use the property ClientUserId. It is well described in the DocuSign article Embedded Signing.
If you're willing to switch after the envelope is created, see my recent question here that deals with the same issue.
To implement the "security questions", DocuSign offers multiple authentication option. It seems to me that you are looking to use the "ID Check" authentication here
In C#, it would look like this when you try to implement ID Check for a given signer :
signer.RequireIdLookup = bool.TrueString;
signer.IdCheckConfigurationName = "ID Check $";
Lastly, for your question regarding the authentication method and the certificate of completion, the Embedded signing article I mentioned above explains well what happens for the authentication method in the certificate completion below :
The authenticationMethod is an enumerated value that indicates the convention used to authenticate the signer. Since, with Embedding, you are telling Docusign that you are handling authentication this is your way of telling the platform how you authenticated the recipient. This information will also be included in the Certificate of Completion, a PDF that is automatically generated for every completed envelope.
We are using the DocuSign REST services and currently passing in the recipients required to sign the document from two People columns in a SharePoint document library. The client would now like to have it that they have secondary signers, e.g. the original users could sign but if they are not available their assistant must do so. What would be the best solution for this?
I noticed mention of something similar here:
Docusign multiple signers for one signature line
They want this to happen at run time though, so the email addresses get sent on the original request to create the envelope and this solution above speaks more to the concept of creating them via the DocuSign interface which is not ideal for them. Has anyone else tried this?
Do the assistants sign as themselves or on behalf of the original signer? I'm making some assumptions here, but most assistants would have access to their boss' emails, so presumably they'd have access to the DocuSign notifications that comes though. In that case, the assistant could simply sign as the original signer by clicking through to the envelope from the email. While this is usually a bit of an eyebrow raising move in terms of security, the reality is that many partners in law firms already delegate their authority to their PAs to sign on their behalf, and today these PAs have copies of all their bosses' signature images to place on documents.
A slightly better move, if the requirement is for the assistant to sign under their own name, is to go into the envelope from their boss' email and reassign the envelope to themselves. Then they will receive an email and they can sign under their own name and all of this will show in the audit trail.
Either way there isn't anything you need to do from an API perspective apart from ensuring the right features are turned on to allow signers to reassign.
The other option is using Signing Groups, but the groups need to be set up beforehand in the DocuSign account and your API call will enter the signing group ID (under the "signingGroupId" parameter) instead of the recipient name and email. This means either the boss or their assistant could sign if they are in the same signing group, but does not enforce one over the other.
I want to 2 recipient [ user and witness] to use the same device or ip address to sign the document sent via docusign.
Please let me know if i can achieve this in docusign
Have you considered using in-person signing? That would require the "host" of the signing session to be a DocuSign user in your account though, but process operates under the assumption that the signer and witness are at the same location.
Alternatively, this question is asked quite often and what you need to have a serious think about is whether the witness is required at all. In most use cases, DocuSign effectively replaces the need for a witness as DocuSign itself is witnessing the signature, authenticating the recipient and recording all the actions of the recipient for you. In all but legal use cases (like notarization) it's usually found that the traditional witness signature is no longer required as a result.
A question from a non-developer. I am getting a website made of my business where our product is to email signed documents. I want to automate that process by incorporating Docusign.
The documentation is written for developers, so I just want a laymen's version.
Can I get the API to sign a document with my signature, add the signed date and two other custom fields and then email to the customer?
The way I think it may work is by creating a template in docusign and adding the tags then the api going to work to email it.
Am I correct?
Technically speaking, the scenario you describe is achievable with the DocuSign REST API -- with a couple of caveats:
The API call would have to supply the document(s) as part of the API call. It's not currently possible to auto-apply signatures with the API when you're using DocuSign Templates as a basis for creating the envelope.
Regarding the "two other custom fields" you want to auto-populate on the document(s) via the API at the same time that the API auto-applies your signature and signed date -- the only two types of fields that are supported in this scenario are Text and Checkbox.
Although you can't use a Template to specify the document(s), fields/tags, recipients, etc. -- all of this can be specified via the API call itself. Assuming you have control of the document(s) being sent, you could use DocuSign's "anchor text" feature to specify where each field/tag should be placed in the document(s).
Keep in mind that the audit trail for the Envelope will show that the API auto-applied the signature to the document(s), rather than an actual human purposefully and intentionally (electonically) signing the document(s) themselves. I'm no lawyer and this is certainly not intended to be legal advice -- but common sense may imply that a programmatically-applied signature might not be considered equal to a signature that a human actually purposefully and intentionally (electronically) applied themselves. IMO, one of DocuSign's strengths is the audit trail information recorded for each transaction that can be used to prove the authenticity of each signing transaction -- if you start auto-applying signatures via the API, you might risk losing that ability to prove the authenticity of the transaction(s).