Skip to main content

iChris (Chris21)

Import your workers and their job assignments from iChris (Chris21), the HR platform. Connecting iChris keeps your Oho worker list in step with your HR system of record, so people don't have to be added in two places.

What it imports​

Workers and their current position assignment from iChris. Optionally, licence and credential records can also be imported when configured.

What you'll need​

Credentials from your Chris21 administrator:

  • Base URL — your environment's API endpoint (production or staging)
  • Username and Password — your Chris21 account credentials
  • Client ID and Client Secret — used to generate a secure authentication token

There's no file to manage. Oho connects directly to the iChris API.

How it runs​

Oho syncs from iChris on the schedule you set. It polls for HR record changes since the last sync, so new starters, role changes, and terminations in Chris21 flow through to Oho automatically.

Importing credentials (optional)​

When enabled, Oho can also import licence records (e.g. WWCCs, police checks, AHPRA registrations) held in Chris21. To enable this:

  1. Set Include Credentials to on in the integration settings
  2. Map each Chris21 licence code (e.g. NPC, WWC, AHPRA) to the corresponding Oho credential type

Only licences with a mapped code will be imported.

Importing position requirements (optional)​

Chris21 already records what a position requires — flags on the position record such as "Working With Children check required" or "National Police Check required". When enabled, Oho reads those flags and sets them as the requirements for the position, so every worker in that position is checked against them and anything they don't hold shows on their profile as a missing credential.

Chris21 records the requirement generically ("a WWC check is required") while Oho tracks the specific credential (a WA check is not a NSW one), so you tell Oho which credential each flag means. To enable this:

  1. Set Sync Position Requirements to on in the integration settings
  2. Add a rule for each requirement: enter the position property name and the value that means "required", then choose the Oho credential type it stands for
  3. Where the flag doesn't say which jurisdiction's credential is needed, set only for on the rule to a country and/or state, and add one rule per jurisdiction — pdtwwcrq = Y only for WA → Working With Children Check (WA), and the same again for NSW, VIC, and so on

Every rule that matches adds a requirement, so a position needing both a police check and a WWCC matches two rules. A rule with only for left blank applies to every position, which is what you want for a nationally consistent credential like a police check.

Chris21 is the source of truth for the positions it reports

Each sync replaces the position's requirements, so turning a flag off in Chris21 removes the requirement in Oho on the next run — don't edit those positions' requirements in Oho by hand. Positions Chris21 has no detail record for are left untouched.

Data ownership​

Chris21 is the source of truth for the workers it syncs — their identity, employment, position, and (when credential import is on) the licences they hold. Oho refreshes these from Chris21 on every sync, so maintain them in Chris21; a change made to one of these fields in Oho is replaced on the next run.

Two credential details are owned by Oho instead: the expiry date — Oho detects changes when it re-verifies a credential and writes the new date back to Chris21 — and the name a credential is checked under, which you can edit in Oho so verification matches (this one isn't written back). Credentials a worker gains when you hire them from an applicant are also written back into Chris21 so it stays complete. And whether a credential is actually valid is always decided by Oho's verification against the official register — never by the status held in Chris21.

See Keeping your data in sync for the full picture of how ownership works across every connected system.