...
Section |
---|
Basic ConceptsOrganization and other Core DataWhen 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:
EnvelopesBasic 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:
Recipient Types:
* optional feature |
Section |
---|
Examples of Signing WorkflowsSimple Workflow (1 Signer): Workflow (1st Signer, Reviewer, 2nd Signer) Bulk Workflow (1st Signer, Bulk Signers) Simple Automatic Workflow (1st Automatic Signer)
|
Section |
---|
Quick-Start GuideWith 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 LoginThe 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. |
Section | ||
---|---|---|
Sending your first EnvelopeUse 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. (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.
|
...