Skip to main content

Connect Your NCC Account

National Crime Check (NCC) is an accredited provider that lodges and obtains nationally coordinated police checks. Connecting your own NCC account lets Oho submit checks against it, so results and billing stay with your organisation while the tracking, consent trail, and decisions live in Oho.

You only need to do this once. After it's connected, every police check you request pre-fills with these details.

What you'll end up with

A connected NCC verification source that pre-fills every police check request, and an NCC ID returned by Oho for each check you submit.

Before you start​

  • An NCC account you can sign in to, with access to the co-branded site your checks should be processed under
  • Admin access in Oho — verification sources sit under Admin. If you don't see the menu item, ask your Oho administrator
  • A list of the organisations this NCC account should cover. One source covers one NCC account; the organisations you pick share it

Step 1: Get your Site ID from NCC​

  1. Sign in to your NCC account.
  2. Go to Settings → Co-branded Sites.
  3. Copy the Site ID for the site you want your checks processed under.

Keep it handy — you'll paste it into Oho in the next step.

Expected outcome: you have the Site ID for the correct co-branded site.

Step 2: Add the verification source in Oho​

  1. In Oho, go to Admin → Verification Sources → Add Source → NCC.
  2. Organisations (required) — tick every organisation whose checks should go through this NCC account. See Which organisations a source covers below, because this choice decides more than it looks like it does.
  3. Fill in the rest:
    • Environment — set this to Production unless you're deliberately testing in the UAT environment.
    • Billing — who pays — the organisation (billed to your NCC invoice site) or the applicant (pays on NCC's page).
    • Industry / Purpose (required) — passed to NCC on every check.
    • Invoice Site ID — paste the value from Step 1. Required when the organisation pays.
  4. Click Save.

Expected outcome: the NCC source appears in your Verification Sources list, not yet connected.

Step 3: Authorise the Oho app​

  1. Still on the NCC setup step, click Connect in the footer.
  2. A window opens on NCC. Sign in with the account associated with your Site ID.
  3. Authorise the Oho app.
  4. The window closes and the step shows as connected.

One authorisation covers every organisation you ticked in Step 2.

Expected outcome: the source shows as connected in Oho.

If you hit a redirect error

A redirect error means your redirect URI hasn't been added on our end yet. Copy the URL from your browser's address bar, send it to support@weareoho.com, then retry this step once we confirm it's added.

Step 4: Request a police check​

  1. Go to Worker Police Checks — or Applicant Police Checks if you're screening a new applicant.
  2. Select the verification source. The Organisation and Who pays fields fill in from Step 2 and are read-only — they belong to the source, not the check.
  3. Enter the purpose of the check.
  4. Click Request. Oho returns an NCC ID for the check.

Expected outcome: the check is submitted and Oho displays an NCC ID against it.

How to confirm it worked​

Open the police checks list in your NCC account. The new check appears there, and its ID matches the NCC ID shown in Oho.

Which organisations a source covers​

The organisations you tick share one NCC account — one environment, one Site ID, one sign-in. The setup fields apply to all of them; you don't configure each organisation separately.

That gives two rules worth knowing before you set this up:

  • A second NCC account needs a second source. If one business unit has its own NCC account and Site ID, give it its own NCC verification source rather than adding its organisation to this one.
  • An organisation not on the list has no NCC account of its own to fall back on. What happens next depends on how many organisations the source covers:
    • Covering exactly one organisation: every check from this source uses that organisation's NCC account and invoice site, whichever organisation the worker actually belongs to. Nothing warns you — it simply bills the covered organisation.
    • Covering several: a check for a worker in an organisation none of them matches has no account to route to. It stays Requested with no NCC ID and never reaches NCC. See Common questions on Run a police check.

So tick every organisation whose workers you'll run checks for, even the ones you expect to be quiet.

Adding an organisation later​

Ticking a new organisation isn't enough on its own — it has no NCC authorisation yet, so checks for its workers would be skipped.

  1. Go to Admin → Verification Sources, open the ⋮ menu on the NCC source and choose Edit. (There's no Reconnect on that menu — it's a button inside the source, in the next step.)
  2. On the Configure Connection step, tick the organisation.
  3. A warning appears: "1 newly added organisation not connected yet — click Reconnect to cover it."
  4. Click Reconnect in the footer and sign in to NCC again.
  5. Save the source.

Expected outcome: the warning is gone, and checks for that organisation's workers submit normally.

What's next​