Adobe Acrobat Sign Setup

Introduction

This guide explains how to set up Adobe Acrobat Sign integration with Pramata. The integration enables the automatic pulling of ongoing documents from Adobe Sign into Pramata.

Prerequisites

Before you proceed with the integration, ensure you have completed the following steps:

For Adobe Acrobat Sign: (Enterprise-level plan required)

Admin Integration User: Add Admin Integration User for Pramata. Follow the detailed steps provided here.

For Pramata Platform:

Pramata Platform Access: Ensure you have the necessary Admin rights to the Pramata Platform for completing the integration process.

Document Whitelisting with Adobe Sign Webhooks

1. Account-level configuration:
   • All signed documents are sent to Pramata.
2. Group-level configuration:
   • Only signed documents from designated groups are sent to Pramata.
   • Multiple webhooks can be configured per group.
3. Document filtering:
   • Only documents using the configured webhook(s) will be sent to Pramata, based on the chosen account or group settings.

Example

Let's say a company, TechCorp, uses Adobe Acrobat Sign and wants to integrate with Pramata. They have three departments: Sales, HR, and Legal.

Scenario 1: Account-level webhook

• TechCorp configures an account-level webhook to Pramata.
• Result: All signed documents from Sales, HR, and Legal are sent to Pramata.

Scenario 2: Group-level webhook

• TechCorp configures a webhook only for the Sales group.
• Result: Only signed documents from the Sales department are sent to Pramata. HR and Legal documents are not shared.

Scenario 3: Multiple group-level webhooks

• TechCorp configures webhooks for Sales and Legal groups, but not for HR.
• Result: Signed documents from Sales and Legal are sent to Pramata, while HR documents are excluded.

In each scenario, only the documents that use the configured webhook(s) will be sent to Pramata, providing granular control over document sharing based on the company's needs and privacy requirements.

For detailed instructions on setting up webhooks, see Step 3: Configuring Webhook in Adobe Acrobat Sign. Please ensure you complete Steps 1 and Step 2 before configuring webhooks.

Step 1: Adding an Admin Integration User in Acrobat Sign

1. Log in to the Adobe Admin Console as a System Administrator.

2. From the top panel, select Products. Under Document Cloud, choose Acrobat Sign Solutions.
   
   
   

3. In the Product profiles section, click on the Acrobat Sign Solutions link.
   
   
   
4. To add a user, click the Add User button.
   
5. In the Add users to this product profile page, add an Admin user:

   1. Enter the email address. Select from matching existing users or add a new user if the email is unique.

   2. Set the Product Role to Acrobat Sign Account Admin.

6. Click Save.
   
   
   
7. A success message will confirm the user rights update in both the Admin Console and Acrobat Acrobat Sign.

Step 2: Integrate Adobe Acrobat Sign with Pramata

Important Note: Before starting with the steps ensure you're logged out of your individual Adobe Account, as you'll need to log in to Adobe Acrobat using the Integration User credentials (Integration User from Step 1) specifically created for the Pramata Integration.

Adobe Acrobat Sign Connection Configuration in Pramata Platform

1. Open Pramata and go to Admin Console → Integrations Hub → locate the Adobe Acrobat Sign card.
   
2. Click Configure, a Prerequisites pop-up is displayed, complete all Prerequisite steps using the provided link. Once finished, click the I've Completed These Steps button.
   
3. A pop-up window displays the Initial Configuration. To retrieve the Webhook URL, expand the Trigger details section, copy the Adobe Acrobat Sign URL and store it securely. Click Next.
   
   
4. In the Adobe Acrobat Sign Connection Configuration, the following information is auto-populated:

   • Authorize URL 

   • Token URL

   • Refresh URL

   • Scopes

     
      
     
     
5. Important Note: Before proceeding to the next step, ensure you're logged out of your individual Adobe Account, as you'll need to log in to Adobe Acrobat using the Integration User credentials (Integration User from Step 1) specifically created for the Pramata Integration.
6. Click Connect.
7. The system automatically redirects you to your Adobe Acrobat Sign account. If not already logged in, enter your Admin Integration User credentials.
8. On the consent form, select Allow Access to permit the Pramata Integration to:

   • View users in your account

   • Access documents and data on behalf of any user in your account

9. Confirm successful authorization.
   
10. Close the Adobe Acrobat Sign tab and return to the Pramata application. The Adobe Acrobat Sign connection should now be active, indicated by a green icon. Click Finish.
11. Your integration is successfully enabled.
    
    

Step 3: Configuring Webhook in Adobe Acrobat Sign

A webhook in Adobe Acrobat Sign must be configured to automatically send real-time updates when an agreement workflow is completed, directly to Pramata platform.

Webhook Scope - Before you begin with the configuration steps, decide on the scope:

• Account - All signed documents will be sent to Pramata.
• Groups - Only signed documents from designated groups will be sent to Pramata.

Note that, multiple webhooks can be configured per scope (Group).

Configuration Steps

1. Login to Adobe Acrobat Sign as a System Administrator.
2. Select API from the top menu. If you are already an enterprise customer, you may not see the API link. In that case, choose Account.
   
   
3. In the left panel, select Webhooks and click the create a Webhook icon.
   
   
4. In the Create a webhook pop-up window, enter the following details:
   1. Name - Enter a unique name.
   2. Scope - Choose Account or Group (If ‘Group’, select the specific group)
   3. URL - Paste the Adobe Acrobat Sign Trigger URL from step 2.3 of the Integration process.
   4. Events - Under the Agreement list, select the following value:
      • Agreement workflow completed
   5. Notification Parameters - Select the following parameters:
      • Agreement Info
      • Agreement Participant Info
      • Agreement Document Info
      • Agreement Signed Document
   6. Click Save.