---
sourceDocument: Australia Asset Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-asset-management
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia Asset Management
ft:clusterId :
- itam
bundleId :
- itam
workflow :
- Technology
---
# Integrate with Docusign at Organization level
# Integrate with Docusign at Organization level {#ariaid-title1}
* Release version: Australia
*
* Updated March 12, 2026
*
*  10 minutes to read
Integrating your Software Asset Management application with the Docusign service at the organization level enables you to track your software subscriptions and envelope consumption data.
Note:
Integration with Docusign at the organization level is done using the Data Feed API, so the user's last activities aren't tracked as part of this integration.
For more information about the Docusign service, see [the DocuSign Developer site](https://developers.docusign.com/ios_sdk/developer.html).
Important:
Minimize security risks and protect information by granting access only to the necessary user or API permissions.{#integrate-with-docusign-org__table_kcp_jts_nbc__entry__3}
| Process | Required user role in the Docusign application | Authentication scopes |
|-|-|-|
| Download subscriptions | admin | No scopes |
| Download consumption | admin | No scopes |
[Table 1. Minimal user permissions]
{#integrate-with-docusign-org__table_kcp_jts_nbc}
This process is applicable for Zurich patch 4, Software Asset Management - SaaS License Management (sn_sam_saas_int) 16.0.8, and Software Asset Management (sn_itam_samp) 2.1.0 version onwards.
## Register a Docusign application {#ariaid-title2}
Register a Docusign application through the Docusign admin portal.
### Before you begin
Docusign Role required: admin
### Procedure
1. Log in to your Docusign demo (non-production) account.
You can use any subaccount for logging in that is later promoted to the corresponding production account.
2. Go to the Admin tab.
* If you already have an API integration key from a previous integration ready for use in production, skip to [step 15](https://servicenow-prod.fluidtopics.net/xFMHE71bot4wyZulN2YStQ#register-docusign-app-org__docusign-prod-login).
* If you don't have your API integration key saved, you must generate a new one.
{#register-docusign-app-org__choices_x3n_thm_lhc}
3. On the side navigation pane, select Account Profile and copy the Organization ID to secure it for later use. {#register-docusign-app-org__org-id}
{#register-docusign-app-org__org-id}
4. Navigate to INTEGRATIONSApps and Keys.
5. In the Apps and Integration Keys section, select Add App and Integration Key.
6. On the Add Integration Key form, enter a unique name for your application in the App Name field and select CREATE APP.
7. On the profile page of your application, select Third-party integration key in the Integration Type field.
8. Copy the value of the Integration Key and secure it for later use.
Important:
You must request the Docusign support team for enabling the Data feed API on the integration key that you're generating. If you're using an Enterprise Pro plan, the Data feed API is free for you with organization management. If you're using a low-tier plan, you can opt for organization management as an add-on. For further information, contact the Docusign support team.
9. Select Save.
10. In the Apps and Integration Keys section, locate the application that you just created in the App Name list.
11. Select ActionsSelect Go-Live account.
A Docusign login window pops up prompting you to enter the credentials for your Docusign account.
12. Enter your Docusign credentials.
13. Select a production account on the window that pops up prompting you to choose a production account to which you want to promote your integration key.
The Go Live Status field changes to Pending approval. For a successful Go-Live review, your app must meet the requirements for Go-Live for each API that it uses. For more information on the Go-Live review stages, see [Docusign documentation](https://developers.docusign.com/platform/go-live/).
14. After the integration is approved, the Go Live Status changes to View in production.
15. Log in to your Docusign production account and verify that the same integration key has been promoted to the production account. {#register-docusign-app-org__docusign-prod-login}
{#register-docusign-app-org__docusign-prod-login}{#register-docusign-app-org__steps_nt3_n2m_lhc}
## Generate RSA keypair for Docusign integration {#ariaid-title3}
Generate RSA keys to integrate the Docusign application with your ServiceNow instance.
### Before you begin
Docusign requirements:
* Docusign account
* Docusign app configured to integrate with ServiceNow
* Role required: Docusign administrator
{#configure-docusign-account__ul_bgy_qwj_hhc}
### About this task
The integration of Docusign at the organization level enables access to all subaccounts using a single integration key generated in any one subaccount.
### Procedure
1. Log in to your Docusign production content account.
2. Go to the Admin tab.
3. Navigate to INTEGRATIONSApps and Keys.
4. Next to your application, select ActionsEdit.
5. Select Generate RSA and save the Key Pair ID, Public Key, and Private Key for later use.
## Generate a Java Key Store certificate {#ariaid-title4}
Generate a Java Key Store (JKS) certificate for the JSON Web Token (JWT) authentication of your Docusign integration profile.
### Before you begin
Role required: admin
### About this task
The JKS file that you generate is required for uploading to retrieve the OAuth token when you create a Docusign integration profile. For this upload to be successful, one of the following conditions must be true for the glide.attachment.extensions system property:
* If the property value is empty, the upload is successful.
* If the property value isn't empty, then the jks value must be present for the upload to be successful. For example, if the property already has values such as xlsx, json, and so on, then jks must be present too.
{#generate-jks-cert__ul_a4g_gxx_fjc}
### Procedure
1. Open a text editor for code, such as Sublime Text, and create a file.
2. Paste the Private key that you had generated from your Docusign integrator app.
For more information, see [Generate RSA keypair for Docusign integration](https://servicenow-prod.fluidtopics.net/xFMHE71bot4wyZulN2YStQ#configure-docusign-account "Generate RSA keys to integrate the Docusign application with your ServiceNow instance.").
Note:
Make sure to include both the beginning and ending of the private key.
3. Save the file with the .key extension.
For example, privatekey.key.
4. Open the command line interface (CLI) and navigate to the directory where you saved the file with the .key extension.
5. Create a CA signed certificate using your private key by executing the command:
openssl req -new -x509 -key .key -out .pem -days 1095
You're prompted to provide details such as country name and province name.
6. Enter the required details.
7. Create a PKCS 12 file using your private key and CA signed certificate by executing the command:
openssl pkcs12 -export -in .pem -inkey .key -certfile .pem -out .p12
You're prompted to provide a password for the file.
8. Enter the export password or the source keystore password.
9. Create the JKS file by executing this command:
keytool -importkeystore -srckeystore .p12 -srcstoretype pkcs12 -destkeystore .jks -deststoretype JKS
You're prompted to provide a password for the JKS file.
10. Provide the same password for the destination and source keystore passwords.
## Create a Docusign integration profile at Organization level {#ariaid-title5}
Create an integration profile to track software subscriptions and optimize licensing for the Docusign service.
### Before you begin
To create a Docusign integration profile, request the Software Asset Management - SaaS License Management plugin (sn_sam_saas_int) from the [ServiceNow Store](https://store.servicenow.com/).
Role required: sam_integrator
### About this task
An organization level integration profile uses the Docusign Data Feed API that retrieves detailed subscription and consumption data across an entire organization. The Data Feed API aggregates data from all subaccounts under an organization, offering a
centralized view of envelope activity and usage.
How Data feeds work:
* Data feeds are updated nightly based on the site the accounts are in.
* Data for each account is processed every seven days.
* If an organization has multiple accounts, each account is processed on a different weekday. The system randomly selects a few accounts to process each day, so that data is processed daily but for different accounts. For example, Accounts 1 and 2 on Monday, Accounts 3, 4, and 5 on Tuesday, and so on.
{#create-integration-docusign-org__ul_w4w_yxr_djc}
Even if the integration job runs on the same day the envelopes are sent, the data feeds for those envelopes may not be available. After the data feeds are generated, they are included in the API response. The scheduled job
then processes those envelopes during its next run.
If you're using Software Asset Workspace, the option to create the Docusign integration profile in Core UI is inactive.
### Procedure
1. Navigate to the integration profile.
| Interface | Action |
| Core UI | 1. Navigate to AllSoftware AssetSaaS LicenseDirect Integration Profiles. 2. Select New. 3. Select DocuSign Integration Profile. {#create-integration-docusign-org__ol_ijd_bjk_qtb} |
| Software Asset Workspace | 1. Navigate to License operationsUser SubscriptionsDirect integration profiles. 2. Select New. 3. Select DocuSign from the drop-down list. 4. Select Continue. {#create-integration-docusign-org__ol_wjd_bjk_qtb} |
|-|-|
{#create-integration-docusign-org__choicetable_o3p_z3k_qtb}
2. On the form, fill in the fields.
{#create-integration-docusign-org__table_gnm_whv_5fb__entry__2}{#create-integration-docusign-org__row_ksq_rt5_bgb}{#create-integration-docusign-org__row_qnx_rt5_bgb}{#create-integration-docusign-org__row_nn5_st5_bgb}
| Field | Description |
|-|-|
| Display name | Name of the integration profile. For example, DocuSign Integration |
| Integration type | The default value is set to Organization Level. |
| Contract start date | The date on which the contract agreement became effective. This date isn't the same as the date when your Docusign account was created. |
| Profile type | Type of integration profile. This value is automatically set to DocuSign Subscription. |
| Organization Id | The organization ID to which this account belongs. You can find this value in your Docusign account on the Admin tab. Navigate to Account Profile and copy the Organization ID. |
| Renewal period (months) | The frequency at which envelope consumption gets renewed. For example, if you enter a renewal period of three months, then the consumption data is renewed every three months. The renewal period governs the consumption cycle and is separate from the overall contract term. |
[Table 2. Integration Profile form]
{#create-integration-docusign-org__integration-form-title}
3. Review the required user roles or API permissions specified in the Process configuration field for each process to reduce security risks and optimize SaaS licenses.
Note:
For more information about the required roles and scopes, see the [Minimal user permissions](https://servicenow-prod.fluidtopics.net/xFMHE71bot4wyZulN2YStQ#integrate-with-docusign-org "Integrating your Software Asset Management application with the Docusign service at the organization level enables you to track your software subscriptions and envelope consumption data.") table.
The Download subscriptions check box is selected by default and you can't clear it.
The Download Consumption check box is selected by default. You can check the detailed consumption data in the Docusign consumption \[samp_docusign_consumption\] table. The data in this consumption table is in UTC time zone.
4. Select Submit.
A draft integration profile is created.
The Connection \& Credential field appears and is automatically set to
sn_sam_saas_int.Docusign_OAuth_with_JWT.
5. Open the connection \& credential aliases record by selecting the preview icon ![]() next to the Connection \& Credential field and then selecting Open Record in the record preview.
6. On the Connection \& Credential Aliases form, select the Create New Connection \& Credential related link.
7. In the Create Connection and Credential dialog box, fill in the fields.
{#create-integration-docusign-org__table_ujr_ps1_wmb__entry__2}
| Field | Description |
|-|-|
| Connection Information ||
| Connection Name | Name of the connection. |
| Connection URL | This field is automatically set to https://api.docusign.net. |
| Credential Information ||
| Integration Key | The API integration key that you generated in the [Register a Docusign application](https://servicenow-prod.fluidtopics.net/xFMHE71bot4wyZulN2YStQ#register-docusign-app-org "Register a Docusign application through the Docusign admin portal.") procedure. |
| Key Pair ID | The key pair ID of the private key that you generated in the [Generate RSA keypair for Docusign integration](https://servicenow-prod.fluidtopics.net/xFMHE71bot4wyZulN2YStQ#configure-docusign-account "Generate RSA keys to integrate the Docusign application with your ServiceNow instance.") procedure. |
| Audience URI | Enter account.docusign.com as the URI. |
| Keystore Password | Password associated with the uploaded JKS file that you created in the [Generate a Java Key Store certificate](https://servicenow-prod.fluidtopics.net/xFMHE71bot4wyZulN2YStQ#generate-jks-cert "Generate a Java Key Store (JKS) certificate for the JSON Web Token (JWT) authentication of your Docusign integration profile.") procedure. |
[Table 3. Create Connection and Credential dialog box]
{#create-integration-docusign-org__table_ujr_ps1_wmb}
8. Locate the JKS file on your device by selecting Keystore.
For more information on creating the JKS file, see [Generate a Java Key Store certificate](https://servicenow-prod.fluidtopics.net/xFMHE71bot4wyZulN2YStQ#generate-jks-cert "Generate a Java Key Store (JKS) certificate for the JSON Web Token (JWT) authentication of your Docusign integration profile.").
9. Select Create and Get OAuth Token.
10. On the integration profile form, select Validate Connection to verify the connection and credential details of this integration.
Validating the connection verifies the Download Subscriptions APIs.
### What to do next
After the integration connects, your ServiceNow instance automatically creates software models and software subscriptions that are refreshed daily.
After creating an integration profile, view information about the profile in the Software Asset Workspace by navigating to License operationsUser subscriptionDirect integration profiles. You can select an integration profile to view the following related lists. If the following related lists aren't visible for an integration profile in the default view, you can select the custom integration view from the Details tab:
* Software Models
* Scheduled Jobs
* Scheduled Job Results
* Unrecognized Subscription Identifiers
* Software Subscriptions
* Subscription Identifier Exclusion Rule
* Subscription User Exclusion Rule
{#create-integration-docusign-org__ul_o5r_xwy_3hc}
After creating an integration profile, you can define subscription exclusion rules to keep certain subscriptions from license cost calculations. For more information, see [Subscription exclusions for SaaS and SSO applications](https://servicenow-prod.fluidtopics.net/kwS~TWLEZdf67e7UjappHg#subscription-exclusions "Define subscription exclusions for your SaaS and SSO applications to optimize your licensing costs by keeping the excluded subscriptions out of license cost calculations.").
If you want to set up multiple integration profiles with unique connections, create child aliases to manage different configurations and settings for each integration profile. For more information, see [Create a child alias to set up multiple integration profiles](https://servicenow-prod.fluidtopics.net/o5L0ctEzWkFYzYxMhh78ew "Create a child alias to set up multiple integration profiles with unique connections and manage different configurations for each integration profile.").
Create software entitlements for the automatically generated software models to track used software against owned software.
* For more information on creating software entitlements in the Software Asset Management Core UI, see [Create entitlements in Software Asset Management Core UI](https://servicenow-prod.fluidtopics.net/8ZR9KWQ1FY73pUmBw_wZRQ "Create entitlements in the Software Asset Management Core UI application to record your license details and allocate purchased software rights to users or devices.").
* For more information on creating software entitlements in the Software Asset Workspace, see [Create entitlements in workspace](https://servicenow-prod.fluidtopics.net/ZvL7kERffOGQ6dpBU_744w "Create entitlements in the Software Asset Workspace to enter your license details and allocate purchased software rights to users or devices.").
* For more information on creating software entitlements using the Software Asset Management Playbook, see [Create entitlements using the guided walk-through](https://servicenow-prod.fluidtopics.net/rw30KUYxwGuwCDdFtc0mOg "Use the guided walk-through playbook for a step-by-step process of creating entitlements.").
{#create-integration-docusign-org__ul_p5r_xwy_3hc}
Reconciliation also runs on your subscriptions as a scheduled job or on-demand. You can view your reconciliation results in the [License Workbench](https://servicenow-prod.fluidtopics.net/K_GziLbR~smXeeWp0kcdNw "Review reconciliation results in a simplified workbench view.") (Software Asset Management classic application) or the [License usage view](https://servicenow-prod.fluidtopics.net/Ct5YAvsPFESpnVaeLwu5_w "Use the license usage view as a single plane to understand the license position of all software products, remediate non-compliance, view reconciliation results, view, or add removal candidates, and view Software Asset Management related reports.") (Software Asset Workspace). Use these results to determine your license compliance position and to remediate any non-compliance.
* For more information on running reconciliation in the Software Asset Management classic application, see [Run software reconciliation in Software Asset Management classic](https://servicenow-prod.fluidtopics.net/Pic766RsbcGCoP1GsB_9RA "Reconciliation is run as a scheduled job (default is weekly), but you can also run reconciliation manually to reconcile software products in your environment on demand.").
* For more information on running reconciliation in the Software Asset Workspace, see [Run software reconciliation in the workspace](https://servicenow-prod.fluidtopics.net/SUHzxdFqMeO8rQemacW3sA "Reconciliation is run as a scheduled job (default is weekly), but you can also run reconciliation manually to reconcile software products in the Software Asset Workspace environment on-demand.").
{#create-integration-docusign-org__ul_q5r_xwy_3hc}
*[\>]: and then