Skip to main content

Connect iChris (Chris21)

Import your workers and their job assignments from iChris (Chris21), the HR platform. You connect Oho to iChris once, and Oho creates your workers and keeps them in step with iChris on the schedule you choose. When you turn it on, Oho can also bring in the licences and credentials Chris21 holds for each person.

What you'll end up with

Your whole workforce in Oho — each person a worker, with their credentials added and checked — kept in step with iChris, without maintaining two lists.

Before you start​

You'll need:

  • Your workers already recorded in iChris — their names, dates of birth, positions, and (if you want to import them) any licence or credential records.
  • An iChris (Chris21) administrator, or someone who has that access, to generate the connection details in Step 1. These are created inside Chris21, not in Oho.
  • If you plan to import credentials: the list of Chris21 licence codes you use (for example NPC, WWC, AHPRA) so you can match each one to an Oho credential type in Step 3.

Step 1: Get your auth details​

What you'll need for this step

An administrator login to iChris (Chris21). The details below are generated inside Chris21, so if you don't administer it yourself, loop in whoever does before you start.

iChris uses the API key or token pattern — Oho connects directly to the Chris21 API, and there's no file to host or manage. Ask your Chris21 administrator to provide five details:

  1. Base URL — your environment's API endpoint. Production and staging have different addresses; use the one for the environment you want Oho to read.
  2. Username and Password — the Chris21 account Oho signs in as.
  3. Client ID and Client Secret — the registered credentials Oho uses to generate a secure token.

Copy all five somewhere you can paste from in Step 2. For the general pattern and how to keep these safe, see Get your auth details → API key or token.

Technical detail: base URLs, the token exchange, and account permissions
  • Base URLs. Production is https://apz.chris21.com/APZ_PROD_API/ichris.API; staging is https://apz.chris21.com/APZ_TEST_API/ichris.API. Confirm which your tenant uses.
  • Token exchange. Oho authenticates at the /connect/login endpoint and receives a short-lived access token (it expires after roughly an hour) that Oho refreshes automatically. You don't manage the token yourself — only the five details above.
  • Client ID casing. The Client ID must match the value registered in Chris21 exactly, so copy it as-is.
  • Account permissions. The account Oho signs in with reads the people, positions, and (if enabled) licence records you want to import. Scope it to read-only where Chris21 lets you, and to just the records Oho should see.

Hand these points to whoever administers Chris21 — a non-technical admin can skip them.

Treat these credentials like a password

The password, Client Secret, and token all grant access to worker PII — names, dates of birth, and licence numbers. Never post them in email, chat, or a ticket, and hand them over only through a channel your organisation trusts. Rotate them, and revoke the account's access, if this connection is ever removed.

Expected outcome: you have the Base URL, Username, Password, Client ID, and Client Secret from Chris21 copied and ready to paste into Oho.

Step 2: Connect it in Oho​

In the left menu under Admin, click Integrations, then start a new integration.

The Integrations page in Oho

Pick iChris (Chris21) from the list of sources.

Choosing iChris (Chris21) as the source

Paste the five details from Step 1 into the connection fields and click Next.

Entering the iChris connection details in Oho

Expected outcome: Oho confirms it can reach iChris and moves you on to field mapping.

Step 3: Map your fields​

iChris sends its own names for organisations, worker statuses, and licences, so Oho asks you to line each one up with the matching Oho value. During setup you map:

  • Organisations — your Chris21 organisation values → your Oho organisations, so each worker lands in the right place.
  • Worker Status — your Chris21 status values → Oho's ACTIVE, INACTIVE, ON_LEAVE, and TERMINATED, so leavers drop out of your live reports instead of showing as active.
  • Qualifications and credentials — each Chris21 licence code → an Oho credential type. This only appears when you're importing credentials (see Import credentials below).

Oho recognises returning workers by their iChris record ID, carried on source.externalId — not by email. Keep that ID stable in Chris21 and re-syncs update each person in place rather than creating duplicates.

For what each field expects, which are required, and how re-syncs avoid duplicates, see the shared Map your fields reference, and the iChris integration reference for what this connector imports at a glance.

An unmapped value won't land where you expect

A Chris21 organisation or status you leave unmapped won't sort your workers correctly, and a licence code you don't map to an Oho credential type still imports as a record but can't be verified. Map every value the setup screen lists before you save.

Expected outcome: every organisation, status, and licence value iChris sends maps to an Oho value, and each worker has its iChris record ID set as the match key.

Import credentials (optional)​

Oho can also bring in the licence records Chris21 holds — WWCCs, police checks, AHPRA registrations, and the like — so they're ready to verify. To turn this on:

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

Only licences with a mapped code are imported; leave a code unmapped and Oho skips it.

Step 4: Set the schedule​

Choose how often the sync runs, then name it and save.

  • Once — a one-off load to get started. Oho already has your people after it runs, so you can have your Chris21 administrator lock the account's access back down afterwards.
  • Recurring — Oho re-reads iChris on a schedule, checking for changes since the last sync, so new starters, role changes, and terminations flow through automatically with nothing to re-enter. The connection details from Step 1 need to stay valid for future runs.

Setting the sync schedule

Expected outcome: the connection is saved and scheduled, and it appears in your Integrations list.

Step 5: Run & verify your first sync​

Run it now with Save & Run, or wait for the first scheduled run. Once it's run, confirm your people are in: they appear under All Workers, and each credential you imported is checked against its official source straight away (see One-off verification).

The new iChris connection in your Integrations list, run history green

If the run didn't bring everyone in, check the run history and the Common questions below.

Expected outcome: your people are in Oho under All Workers, with their credentials queued for verification.

What happens next​

  • Your people appear under All Workers, ready for checks.
  • To keep those checks current, add a verification source for the credential types you hold — synced credentials then verify at the register automatically.
  • If you set a recurring schedule, you don't re-import by hand — change it in Chris21 and Oho picks it up on the next run.

Common questions​

The sync found nothing. Check the five connection details from Step 1 are current — most often the password has changed or the account's access was revoked in Chris21. Confirm you used the Base URL for the right environment (production, not staging).

Some workers didn't import. Oho matches returning workers on their iChris record ID (source.externalId), and sorts them using the organisation and status values you mapped in Step 3. Check those values are all mapped and that the record ID is populated in Chris21.

My credentials didn't come in. Make sure Include Credentials is on and that each Chris21 licence code is mapped to an Oho credential type — unmapped codes are skipped.

I don't see Integrations. This is an admin area — if it's not in your menu, ask an admin in your organisation, or contact support@weareoho.com.