We are announcing that a new integration is live within the Synqly ecosystem. As security operations teams work to extend identity visibility across every system that touches the workforce, we remain focused on giving our customers fast access to the identity providers their end users depend on. We have introduced Greenhouse Identity as a supported provider. Vendor customers can now integrate with Greenhouse Identity through the Synqly integration platform. This addition enables security vendors to work with normalized identity and access data from an organization’s recruiting and hiring layer, creating immediate value for end users who manage their talent acquisition workforce in Greenhouse.
Greenhouse Identity is Greenhouse’s hiring and talent acquisition platform, providing applicant tracking, structured interviewing, and onboarding, along with identity data such as users, groups, and access records for organizations managing their recruiting workforce. Because hiring platforms hold accounts, roles, and access events for recruiters, coordinators, and hiring managers, Greenhouse Identity is a meaningful source of identity context for any team building identity governance, threat detection, or security operations features. As a supported Synqly identity provider, Greenhouse Identity becomes a standardized source of user and access intelligence rather than a one-off connector that each vendor has to build and maintain alone.
Synqly customers can use this integration to perform essential identity data functions directly within their own products. The connector operates in the Identity and Access Management category and allows vendors to retrieve a single user, query a list of users, or enable or disable a user in a customer’s Greenhouse Identity instance. Each user record is returned wrapped in an OCSF Entity Management event, so the identity data arrives in a normalized, standards-aligned format that downstream detection and reporting tools can consume without custom parsing. By disabling or reenabling a user through the same connector, OEM customers can also support identity-driven response actions, not just read operations.
The practical value of this connector is that it brings workforce identity context into active security operations. By integrating via the Synqly unified API, we enable our OEM customers to support Greenhouse Identity as a source of users, groups, and access events without writing or maintaining a custom adapter. Customers can incorporate this identity and access context into their SIEM, their threat detection logic, and their broader security operations workflows, enabling identity-aware security operations across the organizations they serve. Synqly handles authentication and connection management, so product teams can focus on the security insight they deliver rather than the plumbing of yet another identity API. For background on why teams choose a unified API over custom builds, see our overview of the Synqly Mesh Integration Platform.
This release also reflects a broader pattern in how modern security teams think about identity. Recruiting and hiring systems are often outside the traditional identity perimeter, yet they hold real accounts with real access. Bringing Greenhouse Identity into the same normalized pipeline as your other identity sources closes a visibility gap that attackers are happy to exploit. When you can query users and access events from Greenhouse alongside the rest of your identity providers, your detections and your access reviews reflect a more complete picture of who can do what inside the business.
For OEM customers, the speed advantage is just as important as the coverage. When an end user asks whether your product supports Greenhouse Identity, the answer can be yes without a multi-week engineering project, because Synqly already handles the connector, authentication flow, and OCSF normalization. Product and engineering teams can enable Greenhouse Identity, validate it against a live tenant, and ship support to their own customers on a far shorter timeline than a hand-built integration would allow. As the catalog of identity providers in the Synqly ecosystem grows, the same pattern repeats, so each new request to integrate with an identity source becomes a configuration step rather than a fresh development effort. That is the core promise of building integrations once and reusing them across every provider your customers ask for.
For teams ready to implement this capability, we have published documentation that walks through the setup process end-to-end. You will find detailed configuration steps and the available endpoints in the Greenhouse Identity Configuration Guide within the Synqly documentation. We encourage current and prospective customers to explore how the ability to integrate with Greenhouse Identity can strengthen their own product offerings. You can also browse the full set of supported providers on our integration partners page, or review the Identity and Access Management connectors to see how Greenhouse Identity fits alongside the rest of the Synqly identity ecosystem.


