If I set the recipients to get Access Code through email, then do I need to program separately to send the email with access code or Docusign API will automatically send the access code email to all recipients?
Also do I need to enable any setting from my DocuSign account to turn on this feature? I have a developer Docusign Account.
When using the Access Code authentication feature, it's up to the sender how to actually get the code over to the signer. For example, if you have their phone number you can call them and give it to them. Or you can instant message them or send an SMS, or some other means. In general though I would shy away from sending them the code through email as that pretty much defeats the purpose of multi-factor authentication (i.e. if someone has compromised their email they will get both the signature request email AND the access code email).
Similarly, the SMS Authentication feature is used the same way but in this case the code is explicitly sent to their mobile phone number. With Access Code it's up to you how to provide to the recipient.
Related
Using the REST API for remote signing and it's been working great for about a year now.
We have a user of our system that wants to send documents for e-signature, and I'd like to limit their access to their own documents, let them get the notifications of document completion, etc.
I know I can create additional users in the admin section but I'm not sure of where to look from there. Is any of the rest possible?
Yes, add the person as a regular (not admin) sender in your DocuSign account. They'll only be able to see envelopes (transactions) that they sent.
They can also see envelopes that were explicitly shared with them by another sender
Added: authenticate as a different person
Your API application sends envelopes by using the credentials of an account member. If this is a non-person such as "finance#yourCompany.com" then we call that a "system user."
Your question was how to send envelopes from a sender who is not an administrator. The answer is to authenticate to the DocuSign API as that person. This can be done with the OAuth JWT or Authorize Code grant flows.
Ask a new question if you have more questions on how to do this.
I am trying to integrate Docusign in my Web application. The website workflow will be as follows:
Users visit my website and log in.
Users will be given the option to choose Docusign Templates.
After selection, users need to sign that document.
After a successful signing, the signed document is sent to some authority.
My problem is how can I link my users to Docusign to sign. Does every user needs to have an account for embedded signing?? I need some help in understanding the flow of authentication and signing in DocuSign REST API. I have gone through the documentation but didn't understand properly. When I try to use the auth grant GitHub code to understand the flow. After logging in, it throws a null pointer exception. Please, someone, help me.
You can find code example in different languages to do what you're asking (sign from a template). You will want to use embedded signing so that the user sign as part of the app and not remote signing (via email).
As for your authentication question, no, signers never need to be part of the account. The sender can be a single user that is "sending" envelopes that are embedded in the app. So while there's no sending technically, you can think of it this way.
Hope this makes sense, please ask additional questions if not clear
recipientID is a GUID uniquely used to identify a recipient in DocuSign. When you create an envelope, each recipient should have one.
"and If the same name+email combination comes again, will it get the same signature or generate a new one?" It will remember it if they have an account.
At my company, we are implementing some parts of DocuSign, and have run across a scenario we believe the REST API does not support.
There are times where user's in our system change email addresses. We want to push this change to DocuSign for the user, without the user ever requiring to log in to DocuSign and manually change their email address via the console. This, of course, changes the username the user authenticates with on the login page of DocuSign.
Is it possible, using the DocuSign REST API, to change a user's email address (which in effect changes their login name do DocuSign)?
The DocuSign system does not support changing the email address through the API (REST or SOAP). This is mainly due to security restrictions - unfortunately your users will need to manually go into the DocuSign Console and go to Preferences to change their email address.
One thing that might make this process a little smoother is to automatically open the Console for your users when they request to change their email address. You can open the Console in an embedded iFrame in your site or app and from there they can change their account info. You would just need the user's credentials (along with the integrator key of the integration) and you can open the console for them.
The third API Walkthrough - Embedded DocuSign Console - illustrates exactly how to do this in 6 different languages (PHP, Java, Javascript, Python, C#, and Objective-C). You just need to make the following call from your environment, with just your accountId in the body of the POST request:
Method
POST
URI
/accounts/{accountId}/views/console
BODY
{
"accountId": "XXXXXX"
}
We are implementing the DocuSign in our application. While signing the envelope in In-Person mode there is an window (popup) to send a copy of the document in an email.
We have entered the email but no email received. Checked settings in the DocuSign portal account but not able to find any setting for this.
Please let us know how to enable the save a copy email in DocuSign.
I would check settings on your side if you are not receiving the emails. Things like security software, spam/junk mail filters, firewalls, etc. that might stop the email from arriving. DocuSign is a widely used platform, if the emails weren't going out it would be publicly known very quickly, and I just tested this myself and I'm getting the emails. I might suggest you call their support department...
I believe there's an issue when sending out documents using REST API and 3rd party
accounts as senders where we try to get our account a cc back and it
doesn't appear in the management system while we get an email. This way the
envelope is not accessible when using our account and basically the only
option is to use the client account again to get the envelope status or
data. This does not reproduce when sending from that 3rd party account
using the DocuSign website. This way we get a correct CC that appears in
the 'completed' folder. It also works fine when sending form out DocuSign
account and setting the 3rd party account as a CC. This way this envelopes
successfully gets to their system. The difference that can be seen from the
API is that when a correct CC to our account is set, the userId is the same
as we can get from login_information request while in the case when we do
not get it into our system, the userId parameter is different but permanent across multiple envelopes sent while testing this way.
These test tell that it's not the case that CC person should be in the same
account with sender to get the envelope in his system. I've tested with 2
independent accounts and they still get CC and envelope access. I believe
that is a glitch or some kind of limitation and would appreciate any kind
of feedback on this.
(Also, is it allowed to send envelopes as other users under our integration if we
have their logins and passwords?)
I believe the system is behaving properly here. In the DocuSign platform, the account that sends a signature request is the one that has complete access to it. If you send a signature request from a given account and you include a CC recipient from a different account, then only the sending account will be able to see the CC in through the management system (i.e. the DocuSign Console).
The CC recipient from the other account will only receive the notification email and since they were not the sender they will not see it in their folders.