Connect Greenhouse to Glean
Give Glean governed access to Greenhouse’s 156 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Greenhouse to Glean in four steps
Admins approve the server once. Everyone in Glean then gets it through the same governed connection.
- 1
Add Greenhouse to Runlayer
Greenhouse isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Glean to Runlayer
Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Greenhouse’s 156 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Glean setup guide - 3
Sign in to Greenhouse
Sign in the way Greenhouse requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Greenhouse from Glean
Greenhouse’s approved tools appear in Glean. Every call is checked against policy and recorded.
Tools
156 Greenhouse tools in Glean
Runlayer policy decides which of these Glean users can call.
Activate user
Reactivate a previously deactivated user so they can sign in to Greenhouse and be assigned to new jobs again.
Add candidate note
Create a candidate note, log an email, or record an activity-feed entry on a candidate.
Bulk activate users
Reactivate up to the bulk-endpoint cap of users in a single request.
Bulk create blocked spam sources
Adds multiple blocked spam sources in a single request, typically used to sync the blocklist from an external security tool.
Bulk create candidates
Asynchronously create many candidate profiles in a single call, typically for HRIS sync workflows that create a batch of candidates at once.
Bulk create custom field options
Asynchronously add many options at once, typically for HRIS sync workflows that replace or extend a dropdown's option set in a single pass.
Bulk create jobs
Asynchronously create many jobs in a single call, typically for HRIS sync workflows that open a batch of requisitions at once.
Bulk create openings
Asynchronously add many openings across one or more jobs in a single call, typically for HRIS sync workflows that open or extend headcount on a batch of requisitions.
Control
What Runlayer can see and stop in Glean
Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.
Gateway policy (available)
Every Greenhouse call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.
OTLP telemetry (available)
Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.
In Glean
- Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.
Frequently asked questions
Connect more