Language

Just to provide some additional details.

- I've not set a language at the package level. Though the language of the sandbox account being used is English.

- My package contains 2 signers where the first one has the language English and the second one has the language French.

- Here's the packageId for reference "AZVWXekc7S0jInyY1t9BiLehJsE".

Hi NazirNoori,

Thanks for the detailed background information and the package ID, it's very helpful for me to understand your scenario and to pinpoint any potential issues.

In a nutshell, the cause of your confusion is that you seems tried to specify the signer "local language". Your understanding regarding to language settings are essentially correct, so we will sort out the facts and confirm your expectations first, then discuss about why I believe the signer local language caused the issue and what this feature is about.

"1. How do I change the language for the email.activate and email.complete templates?"

• Email templates take signer level settings and generate content dynamically in run time. For example, different signers could have different email messages, language settings and signing URLs.

          So you did right by "setting package default language as English, and set signer language as French"

• Signer level settings, if not specified in particular, inherit package level settings

"2. How do I change the language for the consent form?"

• Default consent form will ONLY be attached to the package when package creation. The package level language determines which language version consent form will be automatically added.

          That to say, consent form won't be re-uploaded if you switch package language, you have to recreate a package with another language or delete then manually            upload a new consent.

"3. How do I change the language for all other elements on the UI during the signing ceremony, without needing the user to manually select their language preference?"

• Signing Ceremony UI labels take signer level language. All pages and UI elements should be translated to the signer level language, instead of only the SMS authentication page.
• The exception is if the signer has an OneSpan Sign account, the signer level language will take what he/she set in the sender profile, instead of what package sender specified.

The easiest way to test above statement is that: you can create a testing package with two signers through UI. If you left the package language as English and only specified one of the signer's language as French. You will see the two signers receive email templates and UI labels in different languages.

For local language:

• You only use it when the signer's language is not natively supported in OneSpan Sign.
• This feature allows you to specify an additional language option "local" for email templates and New Signer Experience UI labels, when you contact support and customize your account.
• However, if you didn't specify those email templates and UI labels, it rolls back to English templates. That's why you saw email templates and those custmozable UI elements in English rather than French.

Duo

Thanks Duo, really appreciate the thorough response and explaining things very clearly.

After removing the local language attribute from the signer, I was able to get the email notifications in French, and also the rest of the UI to be displayed in French as well.

I was hoping there would be a way to change the consent form as well, but I understand the limitation why the consent form can only be displayed in one language per package.

Thanks!