Versions Compared

Old Version 33

changes.mady.by.user Unknown User (bimminger)

Saved on

compared with

New Version 34

changes.mady.by.user Manuel Gierlinger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section

Basic Concepts

Organization and other Core Data

When creating an account or trial account on eSignAnyWhere, you are already creating an organization entity (i.e. a tenant). The first user account is created within that organization. This is a design principle of eSignAnyWhere Workflow solution, as it is designed as a multi-tenant platform.

Within that eSignAnyWhere organisation, following administrative objects exist:

Organization OverviewImage Modified
  • Organisation: The organization itself typically reflects the legal entity for which the sender is collecting signatures. The first user's name is used as organization name by default, but the organization name can be configured later on. The organization is also the unit for which the license applies, at least in the SaaS deployment scenarios.
  • User: As mentioned above, during account registration, the user is created within a generated organization structure. Remember that a user is always part of an organization. But within one organization, additional users (depending on your license and select plan) can be added by the organization administrators.
  • Roles & Permissions: We already mentioned above the role "organization administrator". In general, the roles assigned to a user define the permission set of the user, and it is possible to assign more than one role to a user. The role “Administrator” belongs to an administrator of the organization and is automatically granted to the first user of an organization. The “Power User” is a user, who can send envelopes to request signatures. The “Registered Signer” can use eSignAnyWhere as a signing platform to sign his/her documents and can use it as an document inbox. Beside registered signers, unregistered signers (which do not have an account on eSignAnyWhere) can be invited to sign a document; but they cannot log in and don't get e.g. an envelope overview. Beside this three primary roles, the predefined roles "Api User", "Automatic Sealing Sender" and "Developer" can be assigned to a user to use specific product features.  In the roles and permissions guide we go more into details and also explain how to define and use custom roles.
  • Teams: Teams, if included in the purchased package, can be used to group users within an organization. Teams are used to share templates and envelopes in between team members and the teamlead, or within team members. 

Envelopes

Basic Idea: Send a document via eSignAnyWhere to a signer (recipient) and collect the signed document later.

With eSignAnyWhere you are creating envelopes, which define the signing workflow. An envelope can contain one or many documents (all related to the same business case). Those documents are sent to the recipients to collect signatures, to get a receiving confirmation or just to deliver a copy. The workflow can contain sequential or parallel activities. This allows to design your own signing workflows from very basic to complex. In addition, the product supports sending bulk envelopes - a concept where copies of the same envelope are sent to a list of recipients, and all need to sign their independent copy. Also the use of automatic remote signing certificates (stored in an HSM in the premises of the trust service provider) or hiding certain documents from some recipients within a workflow is supported.

The simplest possible signing workflow would be sending one document to one recipient, who has to sign the document.

You can use eSignAnyWhere for simple signing tasks and for complex tasks e.g. signing a project order, which has to be signed by some managers. A lot of features allow you to design many different signing ceremonies and use cases. In addition you can use our SIGNificant product suite to extend your use case possibilities (e.g. use native iOS/Android apps and SDKs, Signature Pads or even biometric signature verification options).

Workflow Capabilities:

  • We call an item within a workflow an activity  - similar to the use of this term in other workflow solutions.   
  • Sequential/Parallel Activities  
    • Sequential activities: The secuence of how actions have to be performed 
    • Parallel activities: all recipients of parallel activities get the invitation to perform the action at the same time. There is no predefined order.
  • The type of the activity is called the action. We support following actions:
    • Sign: the recipient has to sign the document (or can reject it).
      This action can also be used for form filling and approval steps, even without signature fields involved.
    • Receive a copy: the recipient receives a copy of the document. We also call it "Cc".
    • Needs to view: the recipient must open and view the document. No interaction on the document, beside clicking the link, is required to proceed.
    • Automatic Remote Signers: via Namirial TSP an automatic signature/seal is applied to the document*
    • P7M (PKCS#7) Signing: a specific feature to sign with a PKCS#7 signature*
  • Bulk sending*: each recipient will get a unique copy of the envelope
    (e.g. if you want to send out a new company policy, first signed by the responsible manager and then each employee gets a separate copy of the envelope for signing)
  • Document Hidding*: hide certain documents from specific recipients
  • Meta Information: allow to store meta information per envelope (e.g. for hybrid integration; sending envelopes via UI and automated post processing [auto-archive] via finish callback)


* optional feature

...

Section

Examples of Signing Workflows


Simple Workflow (1 Signer):

Simple WorkflowImage Modified

Workflow (1st Signer, Reviewer, 2nd Signer)

WorkflowImage Modified

Bulk Workflow (1st Signer, Bulk Signers)

Bulk WorkflowImage Modified

Simple Automatic Workflow (1st Automatic Signer)

Simple Automatic WorkflowImage Modified



Automatic Workflow (1st Signer, 2nd Automatic Signer)
Automatic WorkflowImage Modified






Section

Quick-Start Guide

With this basic introductions of the quick-start chapter you should be able to register for a trial account, send your first envelope and collect the signed document. Please see the Web UI Guide for more information about how to create and send an envelope here.

Registration and Login

The login page requires your email address and your password to login. If you have too many false login attempts an additional captcha (“i am human”) will appear due security reasons. If you have forgotten your password, you can reset it via the “Forgot your password?” link.

Moreover, you have the link for the registration page to create a new account/organization. On-Premise and private SaaS customers will see the LDAP/SAML option for login if it is configured.

LoginImage Modified


Section

Sending your first Envelope


Use Case Summary: In this example, we are sending a new insurance contract for internal review (just needs to open it), and then to your client to collect a signature. We are therefore using the Web User Interface.


(1) Prepare an example insurance contract and upload the document to eSignAnyWhere to create a new envelope.

Therefore, use your preferred word processing software, prepare some example contract or letter-style document. No requirement for this example to put any specific notation into the document; just add some text. Export the document in .PDF format, or use the Print-to-PDF capabilities.

Log in to eSignAnyWhere with the account just created, and press the button "NEW DOCUMENT" to create a new envelope. In the envelope creator wizard, on the first page, use the file chooser to upload your PDF file.

(2) Design the structure of the signature workflow, by adding recipients.

Therefore, add your line-manager as a first recipient (defined by mail address and given name / surname). As the line manager is defined as reviewer, select the recipient type "Needs to view".

Add a second recipient (the customer), and keep standard recipient type "Needs to sign". 

Proceed to the next page in the envelope creator by pressing the NEXT button on bottom-right. The 2nd page is the "Designer" page. Use Drag&Drop to place a signature field on the document.

Proceed to the third page in the envelope creator, which is the summary page. Review the configuration and press SEND to send an invitation to the first recipient via mail.

As a sender, you see in the envelope list that the envelope is waiting for the first recipient to open the activity.


(3) After the line manager has approved the document, the client gets invited to sign. Details about the signer UI are explained in the Signer Guide, but for the basic scenario we expect the UI does not require big explainations.
Once thee client has signed the document and pressed the FINISH button, you as a sender receive a notification about the finished document.


(4) As a sender, refresh the UI with the REFRESH button within the Web UI. Now you should see that the status was updated to "Completed". Click on the row to enter the details view. Here you can download the signed document and also the audit trail document, which is the process evidence. Usually, when using the Web UI, you would store both the signed document and the audit trail to your electronic documents archive for storage.
There are of course integration options available to collect the signed documents automatically at the end; those are described in the integration chapter.



Info

In this example, we focused on the very basics. We start from a PDF document to avoid complexity of all the different document conversions available. We did not consider that a document can already be prepared with form fields or signature field locations, we did not explain the differences between various signature types and we did not explain the legal implications based on choice of the proper signature method. Those topics, beside many others, will be covered in the next chapters and subsequend pages.


...