The full installation guide for the new Adobe Sign for SharePoint on-premises solution.
The Adobe Sign integration for Microsoft SharePoint provides an integrated solution for creating, sending, tracking and managing electronic signatures. The integration is available for Microsoft SharePoint 2013 and 2016 On-Premise instance of SharePoint. The solution is developed as a farm solution for Microsoft SharePoint and provides:
The Adobe Sign solution can only be installed and configured by a Microsoft SharePoint Farm administrator; you will also need administrative privileges on the SharePoint server to install the solution. Please consult SharePoint documentation and your organization’s SharePoint administrator for additional systems permissions that may be required to install SharePoint farm solutions. To configure the solution, you also need to be an account administrator on Adobe Sign and have access to your Adobe Sign account Integration Key. System requirements below encompass both the server and client components required to successfully install and run Adobe Sign for SharePoint.
The Adobe Sign for SharePoint solution is supported in the SharePoint 2019 On-Premise Classic UI only.
Adobe and Microsoft are currently working to expand support to include the Modern UI.
SharePoint Foundation is not supported.
Private/Incognito browser sessions are not supported by the Adobe Sign package.
Sharepoint has character limitations that you want to keep in mind, specifically when naming files:
Administrators who are identified as “System Account” when they sign in at any site collection should enter their own information in the AdobeSignUserInfo List as follows:
There is a situation that can occur with the previous solutions that can block normal SharePoint users from accessing the site collection.
The problem occurs if:
To correct the problem, remove the web part from the SharePoint page.
To install the on-premise edition of the Adobe Sign for SharePoint package:
7. The script will run a system check. If all is well, click Next
8. The End User License Agreement will be presented.
○ Check the I accept the terms in the License Agreement box
○ Click Next
9. The Web App / Site Collections page will load. Select the Site Collections you want to install the solution to
10. Once the Setup completes, click Next
11. Once the Details page for the deployment appears, you can click Close
Re-running the Setup script will launch the same wizard and system check process.
After the System check, instead of advancing to the EULA page, the script will prompt you to either:
○ Activate – Activate allows the Admin to activate the Adobe Sign solution on additional Sites in the SharePoint environment. When selected, the Web App / Site Collections page loads, displaying all sites where the Adobe Sign solution is not active (step 9 above).
○ Remove – This option will completely remove the solution from all site collections that Adobe Sign has been activated in. Completed document files will remain in SharePoint.
Agreements that are in process will still be active in Adobe Sign, and will complete normally. The completed documents will no longer be returned to SharePoint.
Once the package is installed, there are four additional configuration steps to complete:
New installations require an Integration Key to be generated in Adobe Sign and then entered into SharePoint. This key is the access token that authenticates the Adobe Sign and SharePoint environments to trust each other and share content.
To generate an Integration Key in Adobe Sign:
If you do not see the Integration Key link on your API Information page, please contact your success manager (or adobe sign support) to review your account settings and make the required adjustments to expose this required functionality.
The Create Integration Key interface loads:
Provide an intuitive name for your key (e.g. SharePoint)
The Integration Key must have the following elements enabled:
Click Save once the key is configured.
The Access Tokens page is exposed showing the keys defined in your account.
○ The Integration Key link is exposed at the top of the definition.
The Integration key is exposed:
To install the integration key into SharePoint:
The first step in adding users is granting them access to the Adobe Sign solution. To do this you need to:
○ Adobe Sign Admin: Users who are allowed to configure the Adobe Sign Solution (i.e. complete the settings page and fill the AdobeSignUserInfo list). Only corresponding site collection or web application administrators are allowed to configure this group. Users belonging to his group can access Personal Settings, Account Settings, Agreement Storage, and Template Mappings tabs under Settings page.
○ Adobe Sign User: Users who are supposed to use the Solution configured by site collection administrators. Users belonging to his group can access only the Personal Settings tab under Settings page.
Adobe Sign requires all users that send Agreements have a license to do so in the Adobe Sign system. Upon first use, a user is automatically provisioned in Adobe Sign if they don't already exist. By default, that user is provisioned using the information found in the users SharePoint profile.
Enabling this feature will inform SharePoint to use the values in the AdobeSignUserInfo list for the purpose of creating new users, and understanding existing user sessions to Adobe Sign.
If the feature is not enabled, then SharePoint will use the values associated to the SharePointUser as defined by SharePoint.
Worth noting is that you can associate email addresses (and thus Adobe Sign access) to SharePoint Users that either don’t have a public email or need to use a different email address than their SharePoint email value. (e.g.: Bob@MyDomain.dom is a SharePoint User, but needs to send agreements using the email value HumanResources@MyDomain.dom)
To use list values for auto provisioning, there are two steps to complete:
To update the AdobeSignUserInfo list
To enable User generation from the AdobeSignUserInfo list:
If this option is enabled, an Audit Trail PDF will be returned with the finalized document when any Agreement is completed. The Audit Trail is a summary document of all major events for the agreement (Sent, Viewed, Signed), including user metadata associated with those events (time/date, IP address)
The Audit Trail is always available directly from the Adobe Sign web site. Enabling this feature permits the auto-delivery of the Audit to your SharePoint environment. Redundant, but convenient.
To enable Audit Trail delivery:
Completed documentation can be configured to be deposited in one specific folder for the whole (global) site collection.
If no global folder is designated, the final signed document will be returned to a Signed Agreements sub-folder that will be created in the document library from which the document was sent.
All signed Agreements are always available on the Adobe Sign web site, and are readily available on the Manage Agreements tab.
To configure the global signed Agreements folder:
Adobe Sign supports the idea of relating data between SharePoint Lists and the Agreement form fields.
By using workflows and mapping the list fields to the form fields, you can automatically pre-fill documents before sending, reducing the time for senders and/or signers to complete the form, and reducing the chance for miskeying the data.
Conversely, you can also create a mapping that will extract the form field data from a signed Agreement, and populate a SharePoint list.