# Signer Guide

We are distinguishing two types of signers:

Non-registered Signer: Users that have no account on the NSE Platform
Registered Signer: Users that have an account on the NSE Platform
For most of the chapters within the signer guide, there is no big difference. The user experience, when starting from an e-mail invite, is very similar. We will therefore not mention in all the next paragraphs that it applies for both; we will just highlight in case something is available only for one of the signer types.

How to sign a document
In a standard scenario, the use case is very simple:

- The signer receives an email with a link to the document.
- The signer opens the link contained in the email
- The signer gains access to the document, reads the content and performs the signature
- The signer performs an explicit Finish operation on the document.
- The signer can optionally download the signed document


The signer gets guided through these steps by the signing web application.

## Get access to the document

When clicking the "OPEN DOCUMENT" link or button in the e-mail, the web browser will open and load the web application to collect the signature(s).

Following steps may be shown, depending on how the sender configured the envelope:

### Authentication or Identification

With different methods such as a static access code communicated upfront, an One-Time-Password (OTP) delivered via SMS, Log-In through another platform (the sender's portal application, Log-In with Google or Linkedin, etc.) or even an Identity Provider Platform asking to identify in a video session or other method. When being logged in via another platform, pay attention to the URL to be sure you don't get victim of a phishing mail, and ask the sender via a well-known channel in case you didn't expect a document signature request before you proceed with the authentication.

### Terms & Conditions

A Terms & Conditions ("Agreements") dialog can be displayed before gaining access to the document.
After both steps completed (in case they have been configured), the signer's view will be shown. We call that web application "Viewer". The layout is responsive, so that the available area is used dynamically and filled efficiently.

### Read, Fill and Sign the document

As a signer, you can now read the entire document content. If the sender requested it, you can (or have to) perform form filling activities. By clicking on the signature field, or by field activation through the step-by-step guiding, the signature task can be executed. Note that the screen below is showing one of the simplest signing experiences the software is offering;  we are explaining the different signing experiences in detail in chapter "Signature Types" of this guide.

After the signature has been performed, a representation of the signature will be shown instead of the interactive signature field. Even if the signature does not look like the handwritten signature and may be just a technical representation of the consent, depending on requested or selected signing experience, the signature is embedded into the PDF document according to the "PDF Advanced Electronic Signatures" Standard and based on the ISO 32000. In addition with a process protocol ("audit trail"), or with some signing experience even without that, the sender can give the proof that a document was signed, and also by whom.

### Finish the document

### Download the document

Optional download of the document

## Signature types

### ClickToSign

This is the simplest signature type, with the most convinient user experience. The signer has just to click on the signature field to sign. As it is a pure browser-based signing experience, we consider the "ClickToSign" signature type as one of the "HTML5 signature types" - which doesn't make big difference for you as a signer, but requires careful consideration of configuration of the activity to reach the necessary expression of power.

### DrawToSign

This type allows the signer to draw his signature by mouse, finger or pen. Just an image of his signature is created and embedded into the document. In this case, only the flat picture of the signature and technical parameters of the session are recorded, but no biometric data.  We consider also the "DrawToSign" signature type as one of the "HTML5 signature types".

### TypeToSign

With this type the signer has to type in his name to sign the signature field. The signature itself is printed in a computer font that may look like someone's handwriting, but actually isn't the signer's handwriting itself. It's the third and last one of this guide which we consider as one of the "HTML5 signature types".

### OTP Signature

For the OTP signature there are two OTP channels which can be configured for receiving the OTP:

- SMS
- Email


In case of SMS OTP you can either enter the phone number or leave it empty to let the signer decide on which phone number the OTP should be sent.

After you have opened the envelope and clicked on the signature field, the following window appears:

You can select your country by clicking on the flag. Then you can see how you have to write the phone number.

After entering your phone number you get a sms and the following window appears. There you have to fill in the code which you got via sms. Please have a look at the following figures.

Once you have filled in the code the document is signed.

### SMS-OTP (Phone number is already defined)

In this case the recipient has just to accept the sending of the transaction code and automatically receives a SMS on the phone number which has been chosen by the sender.

Biometric Signature
There are following options available to sign with a biometric signature in NSE:

- Viewer (in a Web Browser) in combination with SIGNificant Device Driver (on Convertibles directly on the screen, or on Desktop PC/Notebook with signature pads)
- Viewer (in a Web Browser) in combination with the SIGNificant SignOnPhone App for iOS, Android and Windows
- App for iOS, Android or Windows (available in App Stores)
- Kiosk SDK (to sign with signature monitor devices)
- 

(1) Viewer with SIGNificant Device Driver

The SIGNificant Device Driver is a local service which can be used for integrating signature capturing devices and smartcards into a webpage. It is an Add-On for WebSigningInterface, Viewer and SIGNificant Biometric Server for the Enroll&Verify step in Web Applications. Does in addition provide the native access for SmartCard support in WebSigningInterface and Viewer.

(2) Viewer with SIGNificant SignOnPhone App

The Biometric Signature requires a smartphone or tablet with the SIGNificant SignOnPhone App. The App is used to record the biometric signature. The smartphone or tablet is required because of security reasons to ensure high encryption and security of the biometric data. The App is available for free download in the App-Stores of iOS, Android and Windows.

(3) App

The signer uses a smartphone or tablet with the preinstalled App. When the signer opens the App Link of the email the app will start automatically and load the document. The biometric signature is natively recorded and encrypted on the tablet or smartphone via the App.

### Disposable certificate

The process of signing with a disposable certificate is different to the process of signing with the signature fields above. Therefore this explanation and figures will guide you through the process of signing with this signature type. First the signer receives an email to sign the envelope. After clicking on the signature field a new window appears that you have to accept the general terms and conditions. The next figure shows you how the agreement looks like.

After accepting all three points of the agreement you get a sms OTP. Enter the code which you got via sms and fill it in the field next to OTP. The next figure gives you an overview of the notification you get.

After entering the correct code you have signed the document successfully.

### Local certificate

If the recipient gets an envelope with a local certificate signature following window appears after clicking on the signature field:

There, the recipient can choose between his/her certificates and sign with them.

### Digital remote Signature

After clicking on the remote signature field following window appears:

After you filled in the user Id you can select the device id and OTP. The following screenshot shows the configuration:

After this configuration you can request a OTP:

Note: This is the configuration if the sender does not fill in the dates for the recipient. If the sender defines the user Id you just have to sign.

### Approver

In difference to the signature fields e.g. ClickToSign etc. the approval field states to approve by clicking on the field.

After successfully approval a imprint will be added to the document stating beside other data the name of the approver.

## Optional features

### Signature Disclosure

If the Signature Disclosure is used, the signer will just get access to the document if he accepts the Signature Disclosure.

### Authentication

When Authentication is used (e.g. SMS, PIN or Windows Live) the signer has to authenticate himself before he gets access to the document. So the content of the document is protected and access is just granted to the signer. If there are more than one authentication methods for the signer available, the signer can select the one he/she prefers.

#### PIN

#### SMS