Data Sources

HaileyHR

HaileyHR API key boundaries, personnel evidence, and troubleshooting.

HaileyHR

Noru connects to HaileyHR with a customer-provided API key to collect personnel and employment evidence for people controls.

Permission reference

Prop

Type

Setup

Create a HaileyHR API key with read access to the personnel fields needed for compliance.
Enter the key in Noru and run the first sync.
Review personnel records, employment status, and onboarding/offboarding evidence.
Map HR evidence to personnel, access review, and training controls.

What Noru collects

  • personnel records and employment metadata exposed by the API
  • status, department, role, manager, start/end dates, or similar HR fields where available
  • provider IDs and timestamps for evidence tracking

What Noru does not collect

  • write access to HR records
  • payroll, compensation, health, or sensitive HR fields unless the API key and collector explicitly expose them
  • documents or attachments unless explicitly supported by the provider API and collector

Evidence produced

HaileyHR evidence supports personnel directory, onboarding, offboarding, employment status, access-review population, and training assignment controls.

Troubleshooting

Disconnect behavior

Disconnecting stops future syncs. Revoke the API key in HaileyHR to remove provider-side authorization.

Scope minimization

Use a dedicated HR API key, restrict it to needed fields where possible, and avoid collecting HR data that does not support a control.