Docusign: Configuring the App Activities Integration

This article explains how to configure the App Activities integration for Docusign.

Overview

App Activities provides you with an API-based solution for out-of-band visibility of all activity made by any user in a connected SaaS application. To provide App Activities with visibility of data within an app, you need to set up an integration with the required application. Once you create the integration, if a field has changed or expired, you can edit it from the Resources >Integrations > Integrated Apps page. For more information, see What is Application Control via API with App Activities.

To configure the App Activities integration, you need to:

Configure the integration within the SaaS application
Create the API connector in the CMA

A CASB license is required for App Activities. This license includes app and data control and App Activities via API. For more about purchasing a CASB license, please contact your Cato representative.

Prerequisites

DocuSign Monitor Add-on in your DocuSign organization
DocuSign plans for both CLM and eSignature

Benefits of Connecting Docusign

After creating this connector, you can view and monitor activity in your Docusign environment. For example:

User logins (successful & failed)
Document creation
Document sent for signature
Envelope completed
Envelope declined
Account settings changes
User account changes
Organization configuration changes

Configuring the Docusign Integration

To configure the Docusign integration, create an application in the DocuSign admin portal.

Step 1: Configure the Integration in the Docusign Admin Portal

In the Docusign admin portal, configure a user and application.

Creating a User

The first step in configuring the integration is to create a user with the required roles.

To create a user:

In the Docusign Admin Portal create a user. For more information, see the Docusign documentation.
Assign the user the Organization Administrator or Security Reports Administrator role.
On the User's page, copy and save the User ID so that it can be entered into the CMA.

Configure an Application

The next step is to create an Integration key and Private key.

To configure an application:

In the Docusign Admin Portal, navigate Settings > Integrations > Apps and Keys.
Click Add App and Integration Key.
Add the following:
- App Name: Choose a name for the app
- Integration Type: Third-party integration key
- Redirect URIs: https://cc.catonetworks.com/redirect/cas/appconnector/callback
- Allowed HTTP Methods: Check GET and POST
Copy and save the Integration Key so it can be entered into the CMA.
In the Service Integration section, click Generate RSA. Copy and save the Private Key so it can be entered into the CMA.

Note: This is only displayed once.
Click Save.

Step 2: Create the API Connector in the CMA

After you have set up an integration with the required application, add the details in the CMA.

To create the API connector in the CMA:

From the navigation menu, click Resources > Integrations.
Click the Configured Integrations tab.
Click New.

The New Integration panel opens.
Select the SaaS Application you want to add.
In the Capability drop down select App Activities.
Add the details created during step one.
If you are integrating with a development environment, check the Is Dev Environment box, if you are integrating with a production environment, leave this box unchecked.
Click Save.

The Docusign consent flow opens.
Grant consent for these scopes:
- signature
- impersonation
- user_read
The app is visible on the Integrated Apps table with a Connected status.

After connecting your APIs, you can track the App activities in the Cloud Activities dashboard. Data may take a few minutes to appear.