Greenhouse

Explore 7 actions and their permissionsExact inputs, sign-in scopes, access limits and approval rules.

With Greenhouse connected, a hire can:

• list jobs and their stages,
• list applications by job, status or recent activity,
• read a candidate (through one of their applications) and their interview scorecards,
• add a note to a candidate's record, for the hiring team,
• move an application to another stage, asking a person first when it's an offer or hired stage,
• be woken when applications to its jobs have new activity.

Hires never message candidates, and never reject or archive anyone: people do that in Greenhouse.

Candidates' personal data: the minimum, unless you widen itCopy Anchor Link

• By default a hire sees a candidate's name and their applications (job, stage, status). Roster asks Greenhouse for nothing more.
• More fields hires may see (ordinary): company, title, tags.
• Sensitive fields hires may see (only if a hire's job needs them): emails, phones, links, addresses, and privateNotes (scorecards' private notes). A sensitive field typed in the ordinary list is refused, so it always takes a deliberate second step.
• Scorecard notes are shown with email addresses and phone numbers taken out.
• Hires are told that personal data stays inside your team.

1. Make API credentials in GreenhouseCopy Anchor Link

Straight there: Greenhouse's API credentials (sign in if asked).

Greenhouse's API signs in with OAuth (its older API keys stopped working in August 2026).

1. In Greenhouse, open Configure → Dev Center → API Credentials and click Create new API credentials. Choose Harvest V3 (OAuth) and name them Roster.
2. Allow only what hires need: listing jobs, job interview stages, applications, candidates and scorecards, and, for hires that write, creating notes and moving applications.
3. Copy the client ID and client secret.
4. Find the ID of the Greenhouse user hires should act as (ideally one named for your team, like Bayt Studio Hiring): hires see what that user sees, and notes appear as theirs.

2. Connect it in RosterCopy Anchor Link

1. Open Integrations → Tools → Add a tool, search for Greenhouse and choose it.
2. Client ID and Client secret: paste them.
3. Act as user: the user's ID from step 1. Left empty, hires act as the integration's own user, which sees your whole organisation.
4. More fields hires may see and Sensitive fields hires may see: leave them empty unless a hire's job needs more.
5. Click Connect.

Roster checks the key when you click Connect. Once it's accepted, the connection shows Connected as your Greenhouse account, and the user hires act as. If it's refused, Roster says what to fix (a mistyped key, a missing permission) and saves nothing.

3. Give hires accessCopy Anchor Link

On the hire's Tools tab, click Give access on Greenhouse:

• Read only: it can list jobs, stages and applications, and read candidates and scorecards.
• Read and write: it can also add notes and move applications between stages. Moving someone to an offer or hired stage always asks a person first: the hire asks in the thread, and when the approver says yes, Roster moves exactly that application, once.
• Jobs: job titles or IDs whose candidates it may see and work on. Leave it empty for every job. Candidates for any other job are refused, even if the hire knows their application.

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "all": {
      "default": false,
      "description": "include closed and draft jobs",
      "type": "boolean"
    }
  }
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "job": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "the job's ID or title"
    }
  },
  "required": [
    "job"
  ]
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "job": {
      "description": "the job's ID or title",
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    },
    "status": {
      "type": "string",
      "enum": [
        "active",
        "hired",
        "rejected",
        "archived"
      ]
    },
    "changedSince": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    },
    "limit": {
      "default": 20,
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    }
  }
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "application": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64,
      "description": "the application's ID, from list_applications"
    }
  },
  "required": [
    "application"
  ]
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "application": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64,
      "description": "the application's ID, from list_applications"
    }
  },
  "required": [
    "application"
  ]
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "application": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64,
      "description": "the application's ID, from list_applications"
    },
    "text": {
      "type": "string",
      "minLength": 1,
      "maxLength": 10000
    }
  },
  "required": [
    "application",
    "text"
  ]
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "application": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64,
      "description": "the application's ID, from list_applications"
    },
    "stage": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "the stage's name or ID"
    },
    "candidate": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "the candidate's name, as list_applications shows it; checked"
    }
  },
  "required": [
    "application",
    "stage",
    "candidate"
  ]
}