What it adds
Supported systems
Preview means the connector is built from the vendor’s published API and tested against it, but not yet against a live customer tenant. Run a test lookup before relying on it, and tell us what you see.
Set it up
1
Open the HR system
Go to Settings → Directory. Under HR system, choose yours.
2
Enter the settings and credentials
Follow the setup checklist on the page, or the guide for your system linked above. Use an account that can see only the fields TruU reads; each guide has a Restricted account section.
3
Test and connect
Enter the employee number (or other lookup value) of someone to test with and choose Test and connect. TruU looks that person up once. The result shows which fields came back, never their values.
4
Check how people are matched
Review Finding people (below), then choose Save changes.
Finding people
TruU never matches people by name. It reads an attribute from the person’s directory record and looks it up in HR.- Match on. Pick the directory attribute (for example Employee Id) and the HR field it matches (for example Employee number). The defaults are the employee ID, then work email.
- Fallbacks. Add up to two more rules. A fallback is used only when the person’s directory attribute is empty, never because a lookup found no one.
- Adjust format. When the two systems store the ID differently, add steps that change the directory value before the lookup: trim spaces, lowercase, uppercase, remove a prefix, strip leading zeros, pad to 6 digits, or keep only the part of an email before the @. A preview shows the result on a sample value.
- Coverage. The percentage next to each rule is how many directory users have a value for that attribute. It counts directory values only; it does not check that those IDs exist in HR. A test lookup checks a real match.
Attributes
The Attributes card lists what TruU can read from your HR system, the HR field each one comes from, and which factors use it. Standard attributes are mapped for every supported system: legal name, date of birth, home address, personal email, personal phone and employment status. Custom attributes add any other field, for use in knowledge questions. Choose Add attribute and pick from the list:- From your HR system: fields TruU found in your tenant. BambooHR lists every field your account can see; Workday and UKG Pro list the fields a test lookup returned, so run a test first.
- Suggested: common fields, not checked against your tenant.
- Fields that are government IDs, tax, bank, pay, benefits, health or other sensitive categories, or details about other people (dependents, emergency contacts), are never suggested. You can still type a field name if you need one.
- Visible to coworkers marks fields like department, job title and location that colleagues can usually see. They make weak knowledge answers.
- Turn on Secret for a field that should only ever be used for knowledge questions. Secret answers are compared in constant time.
When HR is unavailable
- HR has no record of the person, or shows them as inactive: Require active employment fails.
- HR is down, rejects the sign-in, or the person has no value to match on: by default, date of birth, address and active employment checks that read HR are skipped for that verification, so a temporary HR outage doesn’t block everyone.
- Knowledge questions that need HR are offered only when HR has an answer for that person.
If you disconnect
Disconnecting stops all HR lookups and deletes the saved credentials. The confirmation lists the factors that use HR. Those factors keep their settings but stop checking HR:- Date of birth, address and active employment checks that read HR are skipped, as above. They are not switched to your directory.
- Knowledge questions that ask about HR are never offered, so a question set that needs HR is skipped and the next set is used. If no set can be answered without HR, Knowledge isn’t offered.
How it works
- Live, one person at a time. TruU reads HR during a verification, for that person only, and only the fields a factor needs. Nothing is synced or copied in bulk.
- Values are never stored or logged. HR values are compared in memory and discarded. The console only ever shows whether a field came back, never its value.
- Credentials. API keys, passwords and tokens are kept in a managed secrets service and never returned to the console. Every connection change and console test is recorded in the audit trail.
- Limits. Each HR request has a time limit, and repeated failures pause lookups briefly so a struggling HR system isn’t flooded.

