Safeguard Docs
Compliance ConnectorsSetup by categoryHRIS

Greenhouse

Connect Greenhouse to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Greenhouse to collect hris evidence with automated compliance tests, switched on per workspace.

CategoryHRIS
Connect withAPI token
What a connection producesAutomated compliance tests
Greenhouse's guideharvestdocs.greenhouse.io

Connect with an API token

  1. In Greenhouse:

    1. In Greenhouse, open API Credentials.
    2. Click Create new API credentials and select Harvest V3 (OAuth).
    3. Save the credential, then configure only the scopes Safeguard needs to list users.
    4. Copy the Client ID and Client Secret.
    5. Exchange them for an access token with a server-side POST to https://auth.greenhouse.io/token using HTTP Basic authentication and grant_type=client_credentials, then paste the access token into Safeguard.

    Greenhouse's public documentation does not cover every step.

    Source: harvestdocs.greenhouse.io, checked 2026-10-07.

    The permissions Safeguard needs: harvest:users:list.

  2. On Compliance › Connectors, open Greenhouse, click Connect, choose API token and fill in:

    FieldWhat to enter
    Access tokenRequired. Stored encrypted and never shown again.
  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Greenhouse and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

FrameworkEvidenceControlsTests
SOC2Automated testsCC6.2, CC6.33
ISO/IEC 27001Automated testsA.5.16, A.5.18, A.6.5, A.8.23
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4)3
PCI DSSAutomated tests7.2.2, 7.2.4, 8.2.53
NIST CSF 2.0Automated testsPR.AA-01, PR.AA-053

These tests are switched on per workspace by the Safeguard team.

On this page