Skip to main content
Book a demo

Connect Lattice to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Lattice

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

  4. 4

    Use Lattice from GitHub Copilot

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

Tools

22 Lattice tools in GitHub Copilot

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

  • Find ancestors

    Find ancestors.

  • Find employees

    Searches for employees in the user's company by name, work email, and/or department.

  • Find feedback

    Retrieves feedback items the user has visibility into.

  • Find one on ones

    Find one on ones.

  • Find reports

    Find reports.

  • Find reviews

    Retrieves reviews the user is permitted to see, filterable by who the review is about, who wrote it, the cycle, direction, submission/sharing status, and date range.

  • Get current update draft

    Returns the user's current-period update draft, with the questions on the form, any answers already saved, the period bounds, and the cadence.

  • Get draft reviews

    Retrieves the open performance review drafts the user is currently authoring.

See all 22 Lattice 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 Lattice 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