Humaans

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

Connect with an API token

1. In Humaans:

   1. In Humaans, open the API access tokens area in settings.
   2. Create a new token for Safeguard and choose its validity (1 to 365 days, or no expiry).
   3. Select the private:read scope (view access to all data except compensations and documents); do not select any write scope.
   4. Copy the token.

   Humaans's public documentation does not cover every step.

   The fetched API reference lists the scopes (public:read, private:read, private:write, compensations:read/write, documents:read/write, webhooks:manage) and expiry options, but not the exact menu path or button labels. The connector's grants (people: read, job roles: read) are covered by private:read. Humaans emails the token owner before it expires.

   Source: docs.humaans.io, checked 2026-10-07.

   The permissions Safeguard needs: people: read, job roles: read.

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

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Humaans 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.

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