Skip to main content
Book a demo

Connect Docusign to GitHub Copilot

Give GitHub Copilot governed access to Docusign’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot setup guide

Set up

Add Docusign to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Approve Docusign in Runlayer

    Add Docusign from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Docusign’s 30 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Docusign

    Each user signs in to Docusign with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Docusign from GitHub Copilot

    Docusign’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.

Tools

30 Docusign tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 14 read data only and 6 can change or delete data.

  • Cancel workflow instance

    Cancel a running workflow instance.

  • Create envelope

    Creates a new Docusign envelope from an EXISTING Docusign template or from documents provided via a remote URL.

  • Create envelope from template

    PRIMARY TOOL for sending Docusign agreements or envelopes for signature using templates.

  • Get account

    Retrieve account information for a specific eSign account.

  • Get agreement details

    Retrieve detailed information about a specific agreement

  • Get agreement filter skill

    REQUIRED BEFORE A FILTERED getAllAgreements CALL: Call this skill before constructing the filter.

  • Get all agreements

    Retrieves agreements for a Docusign account.

  • Get clm workflow definitions

    Retrieve workflow definitions for a CLM account.

See all 30 Docusign tools

Control

What Runlayer can see and stop in GitHub Copilot

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.

  • Gateway policy (available)

    Every Docusign call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination