Skip to main content
Skip table of contents

Authentication

The authentication setting define the type authentication required by the recipient to view the received document.

image-20251016-133150.png

Documill provides two types of strong authentication:

SMS Pin Code

SMS Pin Code User Experience

Upon opening the document, the recipient will be asked to authenticate.

image-20251016-133550.png

The recipients mobile number must be either provided from the Salesforce record in the MobilePhone field or from the template settings.

image-20251016-134114.png


Clicking on the Send SMS button will send the recipient a text message with a 6 digit code. The code will be valid for 180 seconds, after which the user can request a new one.

image-20251016-134318.png

The user has 3 attempts to enter the correct code. If the wrong code is entered more than 3 times, the authentication will fail and the whole process needs to be restarted.

If the verification is successfull, the recipient can continue to the document from where they can the process.

The provided phone number must contain the recipients country code starting with the + sign. Example format: +35840000000.

SMS Pin Code Template Setup

To enable SMS Authentication, an external workflow must be first enabled in the Workflow settings.

image-20251020-050343.png

When E-signing or Data collect is enabled, the Authentication tab will become available.

image-20251020-050443.png

In the Authentication tab, select SMS pin code.

image-20251020-050508.png

Each recipient will need a phone number, including the relevant country code. The phone number can be set via:

  1. The Mobile field on the recipients record (User, Contact).

    image-20251020-050924.png
  2. In the template settings settings

    image-20251020-051125.png

  3. If a Mobile number is not provided or it is in the wrong format, the following error will be shown to the sender and the process will end.

    image-20251020-051333.png

Bank or Mobile eID

Bank or Mobile eID User Experience

Upon opening the document, the recipient will be asked to authenticate.

image-20251020-051922.png

Upon clicking Start identification, the recipients must choose the desired identity provider from the list bellow.

image-20251020-051945.png

Based on the selection, the recipient will be redirected to the selected identity provider which will handle the rest of the process.

OP Identity provider example:

image-20251020-052144.png

Upon successful identification, the user will be prompted to confirm that the details are correct.

image-20251020-052302.png

After the authentication is completed, the user will be redirected back to the document at which point they can sign or approve the document based on the selected external workflow.

Bank or Mobile eID Template Setup

To enable Bank or Mobile eID authentication, an external workflow must be first enabled in the Workflow settings.

image-20251020-050343.png

When E-signing or Data collect is enabled, the Authentication tab will become available.

image-20251020-050443.png

In the Authentication tab, select Bank or mobile eID.

image-20251020-051544.png

For this type of authentication, no further setup is required. Once the recipient click on the document link, they will be prompted to authenticate with a Bank or mobile eID.

This feature is only available for the following indentification providers:

Aktia, Ålandsbanken, Danskebank, Handelsbanken, Mobiilivarmenne, Nordea, OmaSP, OP, POP Pankki, S-Pankki, Säästöpankki and BankID SE.


Licensing

Additional licenses are required in order to use either authentication methods. For more information, contact sales@documill.com

Custom Implementations

For custom implementation, authentication flow commands are available.

SMS Authentication commands:

startAuthentication

finishAuthentication

Bank or Mobile eID commands:

startIdentification

resolveIdentity

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.