Site settings

To configure the behaviour of the site we will log in to the site administrator account. We will click on the top right of the page where the name of the site to which we belong and we are administrators appears.


This will take us to the screen where we can define the data of our organization:


Where the admin will be able to change data such as:

• Organization name
• Tax identification
• Telephone
• Address
• City
• Postcode
• Region
• Country

He can also access the behaviour settings of the site



In each of the tabs we can define the default behaviour that the platform will have.

General

It allows to set the default behaviour when sending certified emails. In other words, the aspects that we define in these options will be those that the system will take by default, unless we set other options at the user level or at the time of sending an EviMail:

EviMail

It allows to set the default behaviour when sending certified emails. In other words, the aspects that we define in these options will be those that the system will take by default, unless we set other options at the user level or at the time of sending an EviMail:

• Sending and certification options.
• Acceptance or rejection options.
• Custody options.
• Event notification options.

EviSMS

It allows to set the default behaviour when sending certified SMS. In other words, the aspects that we define in these options will be those that the system will take by default, unless we set other options at the user level or at the time of sending an EviSMS

• Sending and certification options.
• Acceptance or rejection options.
• Custody options.
• Event notification options.

EviNotice

It allows to set the default behaviour when sending certified notifications. In other words, the aspects that we define in these options will be those that the system will take by default, unless we set other options at the user level or at the time of sending an EviNotice.

• Sending and certification options.
• Signature process (notification access method).
• Acceptance or rejection options.
• Custody options.
• Event notification options.

EviSign

It allows to set the default behaviour when sending agreements signatures. In other words, the aspects that we define in these options will be those that the system will take by default, unless we set other options at the user level or at the time of sending an EviSign.

• Sending and certification options.
• Signature process:
  • Default signature method.
  • If it should be sign at the time or at the end of acknowledgement of receipt.
  • If the navigation bar is enabled in the signature process.
  • Enabling signers‘ changes: It enables or disables the possibility for a signer to change his data (or another person with access to the notification can sign) with regards to the original.
  • Enable Captcha.
  • JSON of additional questions: It allows to define the additional questions that will appear in all the EviSign that are generated.
  • JSON of signature position: It specifies the position where the signature will be inserted in the final document.
  • Enable delegated signature: Indicates if delegated signature is activated.
    • Enable PIN sending by WhatsApp: Indicates the default value for the PIN sending policy by WhatsApp.
      • Disabled: The WhatsApp channel is not enabled to send the PIN. Corresponds to the Normal delivery policy (by SMS).
      • Enable sending by WhatsApp instead of SMS: The WhatsApp channel is enabled to send the PIN as an alternative to SMS.
      • Enable WhatsApp for sending retries only: The WhatsApp channel is enabled to send the PIN only on retry.
  • Default text to include in the signature request email: You can also choose the default language.
  • Default text to include in the signature reminder email: You can also choose the default language.
  • Default text to include on the web page to start the signature process: You can also choose the default language.
  • Default text to include in the signed document notification email: You can also choose the default language.
  • Default text to include in the rejection notification email: You can also choose the default language.
  • Default text to be included in the email informing of the expiry of the deadline for signature: You can also choose the default language.
  • End URL: Where the address of the page to which the signer will be directed once the process has been completed is reported.
  • Documents that will be attached to the final notification:
    • Nothing.
    • Main document.
    • Attachments.
    • All (Main document and attachments.
  • Documents to be attached to the signature request email:
    • Nothing.
    • Main document.
    • Attachments
    • All (Main document and attachments.
  • Possibility to request the differentiated acceptance of annexes.
  • Number of reminders that the signer will receive until the signature process is completed or the life time has expired.
  • Text of the additional terms: Text that will appear at the time of signature.
• Acceptance or rejection options.
  • Custody options.
  • Additional fields: It specifies the list of additional fields to request when creating the EviSign.
  • Geolocation: It allows to set the value of the default Geolocation parameter at site level. This value will be applied by default to all signers of all Evisigns, unless another value is specified at user or signer level. It supports three values:
    • Disabled: In this case, the geolocation of the browser is not recorded.
    • Enabled: Permission will be requested from the signer at the time of starting the signature process. If the signer agrees, the browser‘s geolocation coordinates will be recorded. If the signer denies the permission, the process may proceed without the coordinates being recorded.
    • Compulsory: Permission will be requested from the signer at the time of starting the signature process. If the signer agrees, the browser‘s geolocation coordinates will be recorded. If the signer denies the permission, the process will NOT proceed. This denial will be reflected in the Affidavit.
  • Event notification options: It allows to specify the events to which the EviSign‘s issuer subscribes. These will be the site-level defaults, so if no user-level defaults or values ​​are specified at the time of sending, these are the values ​​that will be applied.
  • Notification options to interested parties: It allows to specify the events to which INTERESTED parties subscribe in the EviSign. These will be the site-level defaults, so if no user-level defaults or values ​​are specified at the time of sending, these are the values ​​that will be applied. Options are as follows:
    • Sent.
    • FinalNotificationSent.
    • Signed.
    • PartySigned.
    • Rejected.
    • Expired.
    • Failed.
    • Cancelled.
  • Event notification options.
  • Notification options to interested parties.
  • Push Notifications options.

EviPost

It allows to set the default behaviour when sending the postal notifications. In other words, the aspects that we define in these options will be those that the system will take by default, unless we set other options at the user level or at the time of sending an Evipost:

• Sending and certification options.
• Custody options.
• Additional fields: It specifies the list of additional fields to request when creating the EviSign.
• Event notification options.

Password policies

It allows to set the parameters that define the password policy for site users:

• Minimum password length.
• Password format.
• Password regular expression.
• Password expiry time.
• Number of previous passwords that cannot be repeated.
• Activating verification against most common passwords or with data belonging to the user.

Site or user profile settings do not affect web services. They are only default values ​​that are taken in the New EviMail/EviSMS/etc. form.