We would like to prevent our Sales Rep(secondary signers) from receiving the completed/signed email with the signed documents as attachments. Only our external customers should be receiving the email.
Wondering if this is possible through the API or within the admin console setting.
We are using SOAP API by the way.
Thanks in advance.
It's not possible to exclude specific (remote) recipients from receiving the "envelope completed" email from DocuSign. ("Embedded/Captive" recipients won't receive any emails from DocuSign by default -- but this isn't the scenario you're asking about.)
Additionally, whether or not the "envelope completed" email from DocuSign contains the signed/completed documents as attachments is controlled via an account-level setting (located in Preferences >> Features within the DocuSign web console):
Since this is an account-level setting, it's not possible to control this behavior (i.e., whether or documents are attached to the "envelope completed" email) on a per-envelope basis, let alone on a per-recipient basis for a specific envelope -- it's either enabled or disabled for the entire account (at any given point in time).
Keep in mind that even if you disable this setting at the Account-level (so that documents are never attached to "envelope completed" emails), all recipients will still be able to access the completed documents via the link in the "envelope completed" email (which displays the completed documents in the DocuSign web console), in addition to being given the opportunity to print and/or save the documents during their signing session. So, it's not like you're preventing a recipient's access to completed documents merely by not having the documents attached to the 'envelope completed' email.
Related
Is there an eSign Rest API available that can be used to disable sending the completed document as an attachment when the workflow is completed for specific envelopes ? I know that there is a settings in the Admin section that can be used to disable sending completed document when the workflow is completed. But this account level setting will work for all the envelopes being sent out from that account. Is there an envelope level eSign Rest API that can be used to achieve the same thing for specific envelopes ?
As you have noted, the Sending account has a setting to determine if completed documents are attached to the "envelope completed" email sent to the recipients. However, there is nothing in the envelope to override the account setting.
I would recommend using the account setting to prevent the completed documents from being attached to the completion emails (because email attachments are not secure), and instead advice signers to use the prompt at the end of signing to save an account that they can log into to securely download the documents at their leisure. It's also worth noting that if the documents in the envelope are too large, attachment may not take place, making it even more important to use a free signer account to securely access envelope documents.
Are you referring to the completed document being attached and sent to the recipients via email? I'm afraid you can't control this setting. It is individual to the recipient's account and only they can change the behaviour for this
I have researched enough and went through the API and could not find what is the right object to set to not to let users download / print documents once they finish signing. All the documents are submitted using envelopeAPI and controlling all the eventNotifications via api.
Would like to control the following also via API.
Not to send completed email to the recipient.
Once the document is signed, the recipient receives an email as shown below.
What is tried so far -- Tried to change the Email preference for Api user and User and did not see
any difference in notification.
Disable download and print option for the recipient.
when the recipients finish signing they are redirected to a page as shown below.
If possible I would the recipients not be redirected to this. If not at least disable download/print
option.
As a matter of law in most jurisdictions, people who sign using an electronic signature must have the ability to view/download/print the signed document.
That said, you can use an embedded signing ceremony. In that case, you control the emails.
We have a very straight-forward DocuSign integration where the users can add signers and send document for signing from our document management tool and the signer level updates are automatically fetched by tool and available to requester within our tool itself.
We recently ran into a rather unexpected situation with our DocuSign integration, wherein DocuSign updated/changed/resolved one of the signer's email address to a different email address. Thus, whenever we (tool) tried to fetch the updates corresponding to that signer, DocuSign kept returning null pointer exception (as the signer with that email no longer existed for the DocuSign).
On after retrieving the audit details for this envelope, we were able to understand the above issue. This was logged in DocuSign envelope history as "Recipient email resolved". On DocuSign Admin account, this entry is shown as below:
DocuSign Envelope History Screenshot
I have tried to dig into DocuSign documentation (product & API both) to know more about "Recipient email resolved" action but to no avail.
My queries are -
Has anyone run into similar situation in past?
What is the root cause/reason because of which DocuSign automatically resolves (changes) the email address of the recipient?
Is there a way to suppress this behavior? If not, is there a way to retrieve the status update against original email address instead of having to manually update the email in our tool?
Additional Information:
Our tool is built such that it allows the customers to configure their own DocuSign account
The email address rarely changes. This only happens on occasions where the signer has specifically provided DocuSign with their preferred email address and alternates. There's no option for you to suppress this behavior.
You can check the envelope to get the signer information later to see the change if you wish.
Hope this helps
i Am Using Docu Sign demo Sample. with help of Demo Sample i am Creating an Application and Trying to Send Email to my Recipient but my recipient is not receiving any mail. i checked email credential and firewall all are okay.
But i am getting Success status by .
EnvelopeStatus status = client.CreateAndSendEnvelope(envelope);
// If we succeeded, go to the status
if (status.SentSpecified)
{
AddEnvelopeID(status.EnvelopeID);
Response.Redirect("GetStatusAndDocs.aspx", false);
}
Status.SentSpecified is true all time.
i dont know where is the Problem?
Thanks in Advance to Assist me.
Normally when DocuSign recipients are not receiving emails it's because one (or more) of the following reasons:
The email notification is not enabled for the action in question (usually signature request).
Security or spam software is catching/filtering the email before it reaches the recipient.
You are setting the recipient as an embedded recipient.
An invalid or incorrect email address has been provided in the request.
Possible resolutions for each
Check email notification preferences by logging into the DocuSign Console and going to Preferences -> Manage Email Notifications.
Check your security software settings, firewalls, spam/junk mail filtering, inspect logs, etc.
Embedded recipients by default do not receive an email (since they are immediately signing). Making a recipient Embedded means setting the clientUserId property for them. To NOT make them an embedded recipient do NOT set the clientUserId property (don't include it in the request at all)
Ensure the intended email addresses are being set.
Something else that might help debug these types of issues - you can always request the problematic envelope through an API call and inspect it. If using the DocuSign SOAP API you can do this through the RequestEnvelope() call, if using REST look to do a GET call on the /accounts/{accountId}/envelopes/{envelopeId} URI
I would like to add to what #Ergin mentioned that there are Features to enable sending of emails to Embedded receipients.
You should look for these two somewhat confusingly named features:
Suppress Emails to Embedded Signers (checked by default)
Use Envelope Complete Email for (non-suppressed) Embedded Signers
The fix for me was to uncheck the first one and check the second one. This page has a more thorough description:
Suppress Email to Embedded Signers (Check box) – When selected an email completion notice is not sent to embedded signers when envelope signing is completed. This option is only used with the embedded signing function of the DocuSign API and cannot be selected if the Use Envelope Complete Email for (non-suppressed) Embedded Signers option is selected.
Use Envelope Complete Email for (non-suppressed) Embedded Signers (Check box) - When selected an email completion notice is sent to embedded signers when envelope signing is completed. This option is only used with the embedded signing function of the DocuSign API.
As a note you will need to modify this under the DocuSign Admin portal's "Signing Settings".
I am using docusign for sending out document to be signed by the user.
I see that i have an option to set the Content of email for recipients that they receive.
I am trying to see if I can customize the email content when user "Declines" a document.
For example:
I wanted the sender to see as "The customer has declined the document"
and the customer should see "The document is successfully declined"
is this possible if so please provide additional information or reference to online would be helpful
Yes, it is possible to customize the emails that DocuSign sends in response to the "Envelope Declined" event, such that the email that the Sender receives is different than the email that the Signer (Recipient) receives. You can achieve this by customizing the Email Resource File (as described in this guide: https://10226ec94e53f4ca538f-0035e62ac0d194a46695a3b225d72cc8.ssl.cf2.rackcdn.com/docusign-system-default-email-formats.pdf).
Customizing the Recipient's "Envelope Declined" email is described on page 30 of the guide, customizing the Sender's "Envelope Declined" email is described on page 94 of the guide.
(Keep in mind that an Email Resource File is associated with a "Brand" -- so any changes you apply to an Email Resource File will apply to all Envelopes sent using the corresponding Brand.)