How to remove "Enter your email to receive a copy" for in person signing?

Hello ​@Kurt Oberhausen ,

Welcome to the Docusign Community and thank you for posting your concerns!

Which Resource file did you correct? Email or Signing? In the signing resource file there is a section for the “Receive a Copy” for the In-person signing feature, please view page 50: Resource Files 

Let us know if you need further assistance with this.

Best regards,

Nathaly | Docusign Community Moderator
"Select as Best" below if you find the answer a valid solution to your issue!

Hi ​@nathaly.monge,

We did modify the Signing Resource file in order to implement this change. 

To clarify, we made adjustments to the content mentioned on page 50 of the resource file guide. When we set the following XML in the resource file to true, it successfully suppressed the emails:

    <data name="DocuSign_InPersonSuppressEmailCopy">True</data>

However, the issue we are now trying to resolve is that the HTML text "Enter your email to receive a copy" and the input box for entering email are still visible (as shown in the highlighted section of my screenshot). We would like to remove that HTML text to prevent confusion for our customers (because if they did enter something into this, they won’t receive anything). We followed the instructions on page 50 and left blank values in the XML for the resource file, but no changes have occurred in the past 24 hours.

    <data name="DocuSign_HeaderStepGetCopy"></data>

    <data name="DocuSign_InPersonEmailDesc"></data>

    <data name="DocuSign_InPersonEmail"></data>

Is a different value needed to be placed in the XML in order for this HTML text to be removed?

Hello ​@Kurt Oberhausen ,

Thank you for reaching back.

Omitting the code strings does not remove the attributes from the UI. With Resource File Branding, not uploading a given attribute means we use the default value. It is not possible to block the email field from appearing in that window. The closest you can get is to block the window as a whole.

Let us know if you need further assistance with this.

Best regards,

Nathaly | Docusign Community Moderator
"Select as Best" below if you find the answer a valid solution to your issue!

Thanks @nathaly.monge for the information. I am curious about the code string needed to block the entire window. I reviewed the resource file and couldn't find anything. Is the ESRD always tied to this window?

Hello ​@Kurt Oberhausen ,

Thank you for reaching back.

The code <data name="DocuSign_InPersonSuppressEmailCopy">True</data> should have suppressed the whole window, can you send me a screenshot of the actual codding? Apologies for the back and forth.

Let us know if you need further assistance with this.

Best regards,

Nathaly | Docusign Community Moderator
"Select as Best" below if you find the answer a valid solution to your issue!

Hi ​@nathaly.monge,

Here is a screenshot of the code after I downloaded it from the updated Resource File (appears to only show the delta):

I have been giving this more thought, and I believe providing some additional clarity on my intentions might be beneficial. 

Our process begins by initiating an envelope through DocuSign in a desktop/browser environment. Once the "send" button is clicked, our users are directed to log into their DocuSign accounts using the DocuSign app on an iPad. They then receive a notification to begin the hosted session on their iPads. After clicking "host," they will see the following for the recipient:

We need to remove this because there might be sensitive personal information on the document, and if it is sent to the recipient's email (or the wrong email), it could lead to data leakage.

I wonder if the resource file only impacts a browser-based experience. What we are trying to accomplish is through the DocuSign app, which has different text and wording compared to what is inside the resource file. Clearly, there is still some sort of impact, however, as when we did set the setting to 'True', when entering the email, a copy is not sent to the recipient.

I hope providing more clarity around this helps in the discovery of this issue!