E-Signature

It depends on your needs; however, signing in via the web portal allows for the most functionality.  Sign in to the web portal at http://go.middlebury.edu/adobesign/

If you have a PDF on your computer which needs to be signed, the easiest way to sign is likely using the Adobe Acrobat Reader application, which is free.  Please see Adobe’s instructions for e-signing with Adobe Acrobat Reader.

Yes, Adobe has created an Office 365 Add-in which allows for e-signature directly from Outlook.  Please see Adobe’s site for more information on installing and using the Add-In.

Yes, but please refer to Middlebury’s data classification policy for more information on what constitutes sensitive data and recommendations.

Yes, you can create and share templates, either in Adobe Sign or from OneDrive or Google Drive.

All signed documents are available in Adobe’s Document Cloud.  Sign into http://go.middlebury.edu/adobesign/ and go to the “manage” tab to view signed and sent documents.

No, once a document has been signed by all parties, it is no longer available for signature or editing via the Adobe platform.

You can either carbon copy CC colleagues on the document itself or you can share a document after it has been sent or signed.

You can also download the document and upload it to a shared storage location, like Microsoft or Google cloud storage locations.  See more at http://go.middlebury.edu/cloudoverview.

In addition to sending documents for signature, users can also use Adobe Sign to create fill-able web forms which can be re-used.  See Adobe’s Create a web form for more information. 

When sending a document, you can either create a PDF which already has fill-able fields in Acrobat Pro, or you can upload a simple Word document.  Before sending the document, check the “preview and add signature fields” option.  This will allow you to mark the appropriate areas for signature as well as adding other fields.  Adobe Sign will also attempt to automatically add the correct fields into an uploaded document.

An audit reported is a generated document which includes the history of the agreement, including who has viewed and signed it, as well as their IP address.  For more information on audit reports, please see Adobe’s documentation.

There are four different ways in which Adobe can verify the identity of a signer of an agreement. 

1. Email verification - this is the default method applied to all agreements - a signee must verify their email address when signing a document.  This prevents documents from being forwarded.
2. Password - you can add a password to an agreement which is only shared with the signee of the document. 
3. Social - the user is required to authenticate to the document using a Microsoft, Facebook or Google identity.
4. Adobe Sign Authentication - the user must sign in to their Adobe Sign identity to be able to sign this document.  This method only works for other Enterprise Adobe Sign customers or internal Adobe Sign users.

For more information on these methods, please visit Adobe’s web site.