Skip to main content
Book a demo

Connect Ashby ATS to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Ashby ATS 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 Ashby ATS in Runlayer

    Add Ashby ATS 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 Ashby ATS’s 16 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Ashby ATS

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

  4. 4

    Use Ashby ATS from GitHub Copilot

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

Tools

16 Ashby ATS tools in GitHub Copilot

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

  • Add note to candidate

    Add a note to a candidate's profile.

  • Change application stage

    Move an application to a different interview stage.

  • Consider candidate for job

    Create a new application for a candidate on a specific job.

  • Create candidate

    Create a new candidate record in Ashby with a name and optional contact information.

  • Describe object fields

    Look up filterable fields for a given object type.

  • Filter records

    Filter records of a given object type using a structured JSON filter.

  • Get candidate

    Fetch details about one or more candidates.

  • Get interview details

    Get a detailed interview briefing for a specific Ashby interview event.

See all 16 Ashby ATS 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 Ashby ATS 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