folk
Connect folk to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect folk to collect crm evidence with automated compliance tests, switched on per workspace.
| Category | CRM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| folk's guide | developer.folk.app |
Connect with an API token
-
In folk:
- In folk, open the Settings menu in the sidebar and go to the API section (workspace settings).
- Create a new API key.
- Copy the API key and paste it into Safeguard's API key field.
folk documents no scope or read-only option for API keys, and does not state the button labels for creating a key, whether the key is shown only once, or which role is needed. Keys are viewed and managed in the workspace settings under the API section.
Source: developer.folk.app, developer.folk.app, checked 2026-10-07.
-
On Compliance › Connectors, open folk, 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 folk 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 | 2 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 2 |
| PCI DSS | Automated tests | 7.2.4, 8.2.5 | 2 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 2 |
These tests are switched on per workspace by the Safeguard team.
Related
- CRM 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