Safeguard Docs
Compliance ConnectorsSetup by categoryHRIS

Sapling

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

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

CategoryHRIS
Connect withAPI token
What a connection producesAutomated compliance tests
Sapling's guidedeveloper.saplingapp.io

Connect with an API token

  1. In Sapling:

    1. Sign in to Sapling (Kallidus Sapling) as a user with Super Admin permissions.
    2. Go to the Integrations page and open the API Keys tab.
    3. Click Create New Key.
    4. Name the key descriptively (for example Safeguard) and choose whether it expires after 90 days or select Automatically renew the API key when a call is made to that key.
    5. Click Create, then copy the new API key; once you click Save you can no longer view the key.

    Sapling shows the secret only once, so copy it before you leave the page.

    Sapling's public documentation does not cover every step.

    Source: kallidus.zendesk.com, checked 2026-10-07.

    The permissions Safeguard needs: profiles: read.

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

    FieldWhat to enter
    SubdomainRequired. The part before .saplingapp.io in your address.
    API keyRequired. Stored encrypted and never shown again.
  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Sapling 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 testsCC1.3, CC2.1, CC6.21
ISO/IEC 27001Automated testsA.5.161
HIPAA Security RuleAutomated tests164.308(a)(3)1
NIST CSF 2.0Automated testsGV.RR-04, PR.AA-011

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

On this page