- Adobe Acrobat Sign Integrations
- What's New
- Product Versions and Lifecycle
- Acrobat Sign for Salesforce
- Install the Package
- Configure the Package
- User Guide
- Enable Digital Authentication
- Developer Guide
- Advanced Customization Guide
- Field Mapping and Templates Guide
- Mobile App User Guide
- Flows Automation Guide
- Document Builder Guide
- Configure Large Documents
- Upgrade Guide
- Release Notes
- FAQs
- Troubleshooting Guide
- Additional Articles
- Acrobat Sign for Microsoft
- Acrobat Sign for Microsoft 365
- Acrobat Sign for Outlook
- Acrobat Sign for Word/PowerPoint
- Acrobat Sign for Teams
- Acrobat Sign for Microsoft PowerApps and Power Automate
- Acrobat Sign Connector for Microsoft Search
- Acrobat Sign for Microsoft Dynamics
- Acrobat Sign for Microsoft SharePoint
- Overview
- SharePoint On-Prem: Installation Guide
- SharePoint On-Prem: Template Mapping Guide
- SharePoint On-Prem: User Guide
- SharePoint On-Prem: Release Notes
- SharePoint Online: Installation Guide
- SharePoint Online: Template Mapping Guide
- SharePoint Online: User Guide
- SharePoint Online: Web Form Mapping Guide
- SharePoint Online: Release Notes
- Acrobat Sign for Microsoft 365
- Acrobat Sign for ServiceNow
- Acrobat Sign for HR ServiceNow
- Acrobat Sign for SAP SuccessFactors
- Acrobat Sign for Workday
- Acrobat Sign for NetSuite
- Acrobat Sign for SugarCRM
- Acrobat Sign for VeevaVault
- Acrobat Sign for Coupa BSM Suite
- Acrobat Sign Developer Documentation
The Adobe Acrobat Sign for SharePoint Online release notes are ordered below
Support for the Adobe Acrobat Sign for SharePoint Online integration is set to end by June 2024. Consequently, you won't be able to send agreements through this integration after that date. You'll still be able to send agreements from SharePoint using other integrations, such as Acrobat Sign for Power Automate.
We recommend that you remove the Acrobat Sign plug-in from your SharePoint site and transition workflows to other applications.
Web form support
Adobe Acrobat Sign for SharePoint Online v2.0 allows the SharePoint admin to easily capture data and agreements from Acrobat Sign web forms to populate their SharePoint lists without a single line of code.
Acrobat Sign web forms can be used for various internal or external use cases, such as digital onboarding, customer consent, online application, waiver, incident report, etc.
This feature has two elements:
- Web form mapping - A SharePoint admin can view the list of their Acrobat Sign web forms inside of SharePoint, and configure web form mapping rules to automatically route data from completed web form agreements to a designated SharePoint list.
- Signed web form storage - A SharePoint admin can configure a designated folder in SharePoint to automatically store completed web form agreements
Seamless user on-boarding
Admins can enable a new method of user access that grants Acrobat Sign privilege to any SharePoint site member with Edit level permission to use the add-in.
- New installations default to the new "Users with Edit permissions" method
- Upgrading accounts grandfather in the more granular method
- The user permission method can be changed at any time
Upgrading from v1.x
Adobe Sign for SharePoint v2.0 requires additional permissionss to be approved via OAuth (webhooks and web form permissions).
Customers that are upgrading from v1.x must update their OAuth credentials to gain access to these new permissions:
1. Update the Adobe Sign add-in to the 2.x package
2. Update the connection to Adobe Sign:
The person who is both the Office Tenant Administrator and an Adobe Sign Account administrator must bring up the settings page for the sharepoint sign integration tenant.
- Bring up the integration settings
- In the “Connect Adobe Sign” panel:
- Click the Update button (next to Update your Office 365 tenant connection)
- Sign in with the same credentials as before
- The email address used for the original connection is displayed in the first paragraph
- Click the Update button (next to Update your Office 365 tenant connection)
- Close the settings by going back to SharePoint or refresh the window
All sites in the tenant which use the tenant connection should now be able to use web form features
It’s important to close or refresh the settings tab even if you want to immediately start setting up web form mappings after re-authentication with Adobe Sign.
Failure to refresh the settings window produces errors on the web forms tab until you do.
If the SharePoint Administrator and the Adobe Sign Account Administrator are different people, both need to collaborate to configure the solution.
For every site that uses the integration, the person who is both the SharePoint Administrator and an Adobe Sign administrator for that particular site must update the site connection for that site:
- Bring up the integration settings
- In the Connect Adobe Sign panel:
- Click the Update button next to Update your SharePoint site connection
- Sign in with the same credentials as before
- The email address used for the original connection will be displayed in the first paragraph
- Close the settings by going back to SharePoint or refresh the window
Once done, users of that particular site should be able to use web form features
It’s important to close or refresh the settings tab even if you want to immediately start setting up web form mappings after re-authentication with Acrobat Sign.
Failure to refresh the settings window produces errors on the web forms tab until you do.
If the SharePoint Administrator and the Acrobat Sign Account Administrator are different people, both need to collaborate to configure the solution.
Previous Versions
Web form support
Adobe Sign for SharePoint Online v2.0 allows the SharePoint admin to easily capture data and agreements from Adobe Sign web forms to populate their SharePoint lists without a single line of code.
Adobe Sign web forms can be used for various internal or external use cases, such as digital onboarding, customer consent, online application, waiver, incident report, etc.
This feature has two elements:
- Web form mapping - A SharePoint admin can view the list of their Adobe Sign web forms inside of SharePoint, and configure web form mapping rules to automatically route data from completed web form agreements to a designated SharePoint list.
- Signed web form storage - A SharePoint admin can configure a designated folder in SharePoint to automatically store completed web form agreements
OAuth2 based trust relationship
OAuth 2 is used to establish the trust relationship between Adobe Sign and your SharePoint environment. OAuth 2 makes the trusted relationship as easy as authenticating to Adobe Sign from within SharePoint.
Once done, all users within your SharePoint site will be able to freely use the Adobe Sign add-in functionality without each user having to authenticate discretely.
REST based API functionality
Building the application with a REST based solution ensures that all future development in the Adobe Sign system will be readily available for new updates to the SharePoint Online add-in.
Simplified installation process
This add-in installs quickly with little deep technical understanding of the SharePoint objects required. You can have the package installed to a functional state in as little as 20 minutes for most administrators, without having to provide any additional user licensing.
Data Mapping between Agreements and SharePoint
The Adobe Sign add-in includes the ability to push data from SharePoint lists to an Agreement form field, as well as collecting data from completed Agreement form fields and populate that content into SharePoint lists.
Centralized storage for signed documents
SharePoint admins can configure a central folder that will collect all signed agreements from all users in the site collection.
- This patch removes the dependency in the installation process to create custom Adobe Sign groups.
Access to the Adobe Sign solution is now completely governed by the native SharePoint site Owner and Member groups.
- Linkage between Adobe Sign and SharePoint sites now can be performed for all sites at once. "Global" and "Local" scopes for OAuth connection provide necessary granularity
This version is fully backward compatible, and users existing in the Adobe Sign groups will not be negatively impacted by upgrading.