Synqly Now Integrates with Ashby Identity for Workforce Identity and Access Data

We are announcing that a new integration is live within the Synqly ecosystem. As security operations teams work to extend identity coverage across every platform that hosts workforce accounts, we remain focused on giving our customers fast access to the identity providers their end users depend on. We have introduced Ashby Identity as a supported provider. Vendor customers can now integrate with Ashby Identity through the Synqly integration platform. This addition enables security vendors to work with normalized identity and access data from an organization’s recruiting layer, creating immediate value for end users who run their hiring operations within Ashby.

Ashby Identity is Ashby’s recruiting and talent acquisition platform, providing applicant tracking, candidate relationship management, and hiring analytics, along with employee identity data such as users, groups, and access records for organizations managing their workforce. Recruiting platforms quietly accumulate accounts and access credentials for recruiters, coordinators, interviewers, and hiring managers, making Ashby Identity a useful source of identity context for any vendor building identity governance, threat detection, or security operations features. As a supported Synqly identity provider, Ashby Identity becomes a standardized source of user and access intelligence, rather than a custom connector that each vendor must build and maintain on its own.

Synqly customers can use this integration to perform core 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 and query a list of users against a customer’s Ashby Identity instance. Each user record is returned wrapped in an OCSF Entity Management event, which means the identity data arrives in a normalized, standards-aligned shape, and depending on what the provider exposes, that record can include the user’s current groups and roles. Because the data is normalized on the way in, downstream detection and reporting tools can consume Ashby identity records without custom parsing.

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 Ashby Identity as a source of users 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 insights they deliver rather than on maintaining another identity API. Ashby Identity also joins a growing set of identity sources, so customers can standardize on the Synqly Identity and Access Management connectors and add new providers from the same platform over time.

This release reflects how the definition of an identity source keeps expanding. Recruiting and hiring tools sit outside the systems most identity programs watch closely, yet they grant real access to real people. Pulling Ashby Identity into the same normalized pipeline as your other providers closes a visibility gap that is easy to overlook. When you can query users and their groups from Ashby alongside the rest of your identity stack, your access reviews and your detections reflect a fuller picture of who holds access inside the business, which is exactly the context security operations teams need to act with confidence.

For OEM customers, this integration shortens the distance between a customer request and a shipped feature. When an end user runs hiring on Ashby and asks whether your product can see those identities, you can answer yes without committing an engineering team to building and maintaining a direct Ashby connection. Synqly already handles the connector, the authentication, and the OCSF normalization, so enabling Ashby Identity is a configuration step rather than a development project. As more identity providers join the Synqly ecosystem, the same approach scales, and each new provider your customers ask for becomes another supported source rather than another backlog item. Building the integration once and reusing it across providers lets product and engineering teams spend their time on differentiated security capabilities rather than integration upkeep. 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 Ashby Identity Configuration Guide within the Synqly documentation. We encourage current and prospective customers to explore how integrating with Ashby Identity can strengthen their product offerings. You can also browse the full set of supported providers on our integration partners page to see how Ashby Identity fits alongside the rest of the Synqly identity ecosystem.