Ashby
Connect Ashby to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Ashby 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 |
| Ashby's guide | developers.ashbyhq.com |
Connect with an API token
-
In Ashby:
- As an Ashby Admin, open the API keys page in the Ashby web app (app.ashbyhq.com/admin/api/keys).
- On that page an Ashby Admin manages each API key's permissions; give the Safeguard key only the read access it needs.
- Copy the key and paste it into Safeguard.
Ashby's public documentation does not cover every step.
Source: developers.ashbyhq.com, checked 2026-10-07.
The permissions Safeguard needs:
organizationRead. -
On Compliance › Connectors, open Ashby, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Ashby 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 | CC6.2, CC6.3 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
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