Sage HR
Connect Sage HR to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Sage HR to collect hris evidence with automated compliance tests, switched on per workspace.
| Category | HRIS |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Sage HR's guide | developers.sage.hr |
Connect with an API token
-
In Sage HR, create the credential for API key, read-only where it offers that. Sage HR's guide: developers.sage.hr. Sage HR shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. Sage HR does not publish these steps; its support team can confirm them.
-
On Compliance › Connectors, open Sage HR, click Connect, choose API token and fill in:
Field What to enter Subdomain Required. The part before .sage.hr in your address. API key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Sage HR 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.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC1.3, CC2.1, CC6.2 | 1 |
| ISO/IEC 27001 | Automated tests | A.5.16 | 1 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3) | 1 |
| NIST CSF 2.0 | Automated tests | GV.RR-04, PR.AA-01 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- HRIS connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks