UKG
Connect UKG to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect UKG 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 |
| UKG's guide | developer.ukg.com |
Connect with an API token
-
In UKG:
- In UKG Pro, go to Menu › System Configuration › Security › Service Account Administration and create a service account for Safeguard (UKG recommends a service account over a web user).
- On the same Service Account Administration page, grant the service account appropriate permissions for the services Safeguard reads (view only).
- Set the service account's password and paste its username and password into Safeguard.
Where to find the other values:
- Customer API key: The UKG Pro HCM Web Service administrative page. The service account's User API key is on the Service Account Administration page.
UKG's public documentation does not cover every step.
UKG says service accounts need appropriate permissions granted on the Service Account administrative page and points to the Manage Service Accounts guide in the UKG Learning Center (sign-in required) for the creation steps, so the exact button labels and permission names are unverified (the connector's grant list asks for Employee Employment Information (View) and Person Details (View)). The fetched page does not give the web service host name.
Source: developer.ukg.com, checked 2026-10-07.
The permissions Safeguard needs:
Employee Employment Information: View,Person Details: View. -
On Compliance › Connectors, open UKG, click Connect, choose API token and fill in:
Field What to enter Host Required. An address under ultipro.com. Username Required. Password Required. Stored encrypted and never shown again. Customer API key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read UKG 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