Skip to main content
Book a demo

Connect Lever to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Lever

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

  4. 4

    Use Lever from GitHub Copilot

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

Tools

13 Lever tools in GitHub Copilot

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

  • List opportunities

    List opportunities (candidates) in Lever with optional filters.

  • Get opportunity

    Get detailed information about a specific opportunity (candidate) by ID.

  • Update stage

    Move a candidate to a different pipeline stage.

  • Archive opportunity

    Archive a candidate with a specific reason.

  • Add tags

    Add tags to an opportunity (candidate).

  • Remove tags

    Remove tags from an opportunity (candidate).

  • List postings

    List job postings in Lever with optional filters.

  • Get posting

    Get detailed information about a specific job posting by ID.

See all 13 Lever 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 Lever 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