Skip to main content
Book a demo

Connect Pigment to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Pigment

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

  4. 4

    Use Pigment from GitHub Copilot

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

Tools

101 Pigment tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • Add list items

    Add one or more new items (rows) to a dimension/list with their property values in a single operation.

  • Batch share blocks

    Share multiple lists and metrics in a single operation, making them visible and usable across applications within the organization.

  • Calendar add time dimension

    Add a new time dimension to existing Application calendar.

  • Create calendar

    Creates a new gregorian calendar in the Pigment application.

  • Calendar expand

    Expands or shrinks a calendar's date range.

  • Get calendar

    Retrieves detailed configuration of a specific calendar.

  • Calendar remove time dimension

    Remove a time dimension from the Application's calendar.

  • Clear widget preview

    Removes the Draft View preview from a single Board widget for the current user, so the widget shows its saved View again.

See all 101 Pigment 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 Pigment 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