Skip to main content
Book a demo

Connect Box to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Box 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 Box in Runlayer

    Add Box 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 Box’s 35 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Box

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

  4. 4

    Use Box from GitHub Copilot

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

Tools

35 Box tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 11 read data only.

  • Add items to hub

    Adds files, folders, or web links to a specific hub, enabling content organization within collaborative workspaces.

  • Copy file

    Copies an existing file to a destination folder in Box (see Box API Copy file).

  • Copy folder

    Copies an existing folder to a destination parent folder in Box (see Box API Copy folder).

  • Copy hub

    Creates a copy of an existing Box Hub via the Hubs v3 API (POST /v3/hubs/{id}:copy).

  • Create file comment

    Creates a new comment on a specific file.

  • Create folder

    Creates new folders in Box.

  • Create hub

    Creates new collaborative hubs for organizing content around specific topics, projects, or teams.

  • Create metadata template

    Creates a new enterprise metadata template.

See all 35 Box 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 Box 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