In this section you are managing languages for your organization, and manage which languages can actively be used as recipient languages. 

FigureDescription


Localization Settings

  1. Organization languages
  2. Actions


It will e.g. allow to create custom translations for e-mail templates, for those e-mails sent to recipients. Once a language was added, an administrator or another person with permission to edit email templates can translate e-mail templates to the just added language, and ajust them to corporate language. Therefore, it is not necessary to activate the language. Only when a language was finally "activated", all persons who are sending out envelopes can use the language as "recipient language".


Note that this language list is independent of the list of languages available as Web-UI translations in Settings-Account. As the languages which are not selectable as user languages will never be used to send mails for users, we recommend to identify first which e-mails are sent to recipients so that you avoid translating templates intended for users, which anyhow will not be able to configure this language. For a list of languages available as eSignAnyWhere Web UI Languages, see the Language Support overview of eSignAnyWhere.


When sending out an e-mail, the sender can define a "recipient language" which is then the locale for the SignAnyWhere Viewer & for the mails sent to the recipient. Note that the list of languages to which the SignAnyWhere Viewer's UI is translated again is the shortlist of languages in which the eSignAnyWhere Web UI is available - but individual translations can be configured via Customization.zip; and if a recipient language is not available as SignAnyWhere Viewer language, an instance specific fallback language (typically EN) is used for the user interface.