> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/docusign.md).

# Docusign

Use DocuSign data with Cortex Cloud.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

**SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.

**saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the DocuSign connector

To access DocuSign, Cortex Cloud requires the following information, which you will specify during the connection process.

* **Integration Key (Client ID):** A unique identifier generated when you create a DocuSign OAuth application. Cortex Cloud uses this value to identify your integration.
* **Secret Key:** A client secret generated within your DocuSign OAuth application. Cortex Cloud uses the Integration Key and Secret Key to authenticate to the DocuSign API.

Perform the following procedures in the order that they appear below.

#### Task 1: Create a DocuSign OAuth Application

1. Navigate to the DocuSign Apps and Keys page at <https://apps.docusign.com/dev-console/integrations> and log in using your DocuSign account.
2. Click **Add** to create a new integration.
3. In the **Add New Integration** dialog:
   * Enter a name for the integration.
   * Click **Create**.
4. Under **Integration Type**, select **Private Custom Integration**.
5. Click **Save**. Then scroll to the top of the page.

   > The application is initially created in Demo mode. To use the integration in a production environment, click **Submit** to submit the application for review.
6. Wait for the application to be approved. Once approved, click **Switch to Production**.
7. Copy the **Client ID** and store it securely.

   > Do not continue to the next step unless you have copied the Client ID. You must provide this value to Cortex Cloud during the onboarding process.
8. Copy the **Base URI**. Ensure that this URI is allowed in the Cortex Gateway configuration so that SSPM can communicate with the required DocuSign endpoint.
9. Scroll down to the **Authentication** section and create a new **Client Secret**. Copy the generated secret and store it securely along with the Client ID.

   > Do not continue to the next step unless you have copied the Client Secret. You must provide this value to Cortex Cloud during the onboarding process.
10. Scroll down to the **Additional Settings** section and add the following URLs under **Redirect URIs**:
    * `<url-1>`
    * `<url-2>`
11. Scroll down to the **Allow HTTP Methods** section and select **GET**.
12. Click **Save** to save the integration configuration.

#### Task 2: Connect DocuSign to Cortex Cloud

1. In CortexCloud, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for DocuSign.
4. Under **Recommended**, hover over the new DocuSign integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Integration Key (Client ID)** and **Secret Key** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that DocuSign is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/docusign.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
