Skip to main content

Connect Autodesk Product Help to GitHub Copilot

Give GitHub Copilot governed access to Autodesk Product Help through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Autodesk Product Help 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 Autodesk Product Help in Runlayer

    Add Autodesk Product Help 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 Autodesk Product Help’s tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Autodesk Product Help

    Sign in the way Autodesk Product Help requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Autodesk Product Help from GitHub Copilot

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

Tools

Autodesk Product Help tools in GitHub Copilot

Autodesk Product Help reports its tools when your organization connects it, so the list depends on your deployment.

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 Autodesk Product Help 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